[Group.of.nepali.translators] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1877958 Title: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: There are some test cases in ftrace from ubuntu_kernel_selftests that would need some kernel configs to be enabled. bug 1869347 bug 1869349 bug 1869349 We should not treat unresolved test case as a failure, as it's expected to fail with no correlated configs enabeled. https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a #diff-33d74da785cbc5da20f71eb1af106d68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1877958/+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 1878108] [NEW] new upstream release 2020a
Public bug reported: There is a new upstream release of tzdata, 2020, which includes the following: * New upstream release, affecting past and future timestamps: - Morocco springs forward on 2020-05-31, not 2020-05-24. - Canada's Yukon advanced to -07 year-round on 2020-03-08. - America/Nuuk renamed from America/Godthab. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). This is compared to the same output after the updated package got installed. If those are different the verification is considered done. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: tzdata (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: tzdata (Ubuntu Xenial) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Bionic) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Eoan) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Focal) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu) Status: New => Fix Released ** Changed in: tzdata (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Eoan) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Xenial) Status: New => In Progress ** Changed in: tzdata (Ubuntu Bionic) Status: New => In Progress ** Changed in: tzdata (Ubuntu Eoan) Status: New => In Progress ** Changed in: tzdata (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1878108 Title: new upstream release 2020a Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Trusty: New Status in tzdata source package in Xenial: In Progress Status in tzdata source package in Bionic: In Progress Status in tzdata source package in Eoan: In Progress Status in tzdata source package in Focal: In Progress Bug description: There is a new upstream release of tzdata, 2020, which includes the following: * New upstream release, affecting past and future timestamps: - Morocco springs forward on 2020-05-31, not 2020-05-24. - Canada's Yukon advanced to -07 year-round on 2020-03-08. - America/Nuuk renamed from America/Godthab. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1878108/+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 1700810] Re: aptdaemon's crash.py file may no longer be working
This is failing because apport's fileutils function "make_report_path" was renamed to "make_report_file" in September of 2015. So aptdaemon will need fixing in Ubuntu 16.04 LTS and later. ** Changed in: aptdaemon (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: aptdaemon (Ubuntu) Status: New => In Progress ** Summary changed: - aptdaemon's crash.py file may no longer be working + aptdaemon's crash.py file is not working ** Also affects: aptdaemon (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: aptdaemon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: aptdaemon (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: aptdaemon (Ubuntu Xenial) Status: New => Triaged ** Changed in: aptdaemon (Ubuntu Bionic) Status: New => Triaged ** Changed in: aptdaemon (Ubuntu Eoan) Status: New => Triaged ** Changed in: aptdaemon (Ubuntu Focal) Status: New => Triaged ** Changed in: aptdaemon (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: aptdaemon (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: aptdaemon (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1700810 Title: aptdaemon's crash.py file is not working Status in aptdaemon package in Ubuntu: In Progress Status in aptdaemon source package in Xenial: Triaged Status in aptdaemon source package in Bionic: Triaged Status in aptdaemon source package in Eoan: Triaged Status in aptdaemon source package in Focal: Triaged Bug description: aptdaemon includes a file named crash.py which is supposed to create apport problem reports for a given crash. However, searching through bug attachments for aptdaemon bug reports I don't see any with the key "TransactionRole" in any recent bug reports. $ grep -r TransactionRole * bug-1058886/Description.txt:TransactionRole: role-commit-packages bug-1158395/Description.txt:TransactionRole: role-install-file bug-1166875/Description.txt:TransactionRole: role-remove-packages bug-1201054/Description.txt:TransactionRole: role-commit-packages bug-1237851/Description.txt:TransactionRole: role-commit-packages bug-1279716/Description.txt:TransactionRole: role-commit-packages bug-1293334/Description.txt:TransactionRole: role-pk-query bug-1297434/Description.txt:TransactionRole: role-install-file bug-1301063/Description.txt:TransactionRole: role-install-packages bug-1306498/Description.txt:TransactionRole: role-pk-query bug-1380290/apport_crash.log:TransactionRole: role-pk-query It seems likely that either "trans" is null, or something is wrong with aptdaemon's crash handler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1700810/+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 1878098] [NEW] Xenial update: 4.4.221 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.221 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1878098 Title: Xenial update: 4.4.221 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.221 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878098/+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 1874785] Re: xenial/linux-deeplens: 4.15.0-1023.23 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => 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: 1874787 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Packaging - phase-changed: Tuesday, 05. May 2020 18:31 UTC + phase: Building in ppa + phase-changed: Monday, 11. May 2020 16:35 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building + meta:building variant: debs + versions: + main: 4.15.0-1023.23 + meta: 4.15.0.1023.23 -- 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/1874785 Title: xenial/linux-deeplens: 4.15.0-1023.23 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 -- kernel-stable-master-bug: 1874787 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Building in ppa phase-changed: Monday, 11. May 2020 16:35 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building meta:building variant: debs versions: main: 4.15.0-1023.23 meta: 4.15.0.1023.23 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1874785/+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 1837914] Re: restart systemd-jounald fails
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (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/1837914 Title: restart systemd-jounald fails Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: [impact] in some situations, restarting journald causes assertion failure. [test case] intermittently, when restarting journald. See upstream bug for repro details. [regression potential] this adjusts the journal file destructor, so any regression would likely occur when cleaning up journal files and/or stopping/restarting. [scope] this is fixed by commit c377a6f3ad3d9bed4ce7e873e8e9ec6b1650c57d which is included in Focal. This is needed for Eoan and earlier. [original description] While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal /journal-file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837914/+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 1831459] Re: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (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/1831459 Title: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] test case fails because it does not wait for the service to become active before stopping it, resulting in failure to rmmod the scsi_debug module because it's still in use. [test case] check 'storage' test results for systemd in autopkgtest logs, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz [regression potential] low; test case fix only. [other info] detected and reported by @cascardo in bug 1814373 comment 4 and 5, but separate (non-test) systemd bugfix uploaded for that bug so opening this bug to track fixing the test case. larger fixes/improvements to 'storage' testcase in bug 1829347, but those rejected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831459/+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 1862657] Re: systemd autopkgtest 'logind' fails when running with linux-kvm
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (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/1862657 Title: systemd autopkgtest 'logind' fails when running with linux-kvm Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] the logind autopkgtest tries to access /sys/power/state, but because linux-kvm has CONFIG_PM unset, there is no /sys/power/state file [test case] check autopkgtest, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz autopkgtest [13:48:53]: test logind: ---] autopkgtest [13:48:53]: test logind: - - - - - - - - - - results - - - - - - - - - - logind FAIL stderr: grep: /sys/power/state: No such file or directory autopkgtest [13:48:53]: test logind: - - - - - - - - - - stderr - - - - - - - - - - grep: /sys/power/state: No such file or directory [regression potential] regressions would likely involve incorrectly skipped logind test. [scope] this fails for all releases; Xenial, Bionic, Eoan, and Focal. [other info] it's unclear if linux-kvm should have CONFIG_PM (and other config) enabled or not. However, it's not the intention of systemd's autopkgtests to look for missing config in the kernel; the test already skips if 'mem' isn't in /sys/power/state, so it should also skip if /sys/power/state isn't present at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862657/+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 1862232] Re: Long hostname causes networking setup to fail
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (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/1862232 Title: Long hostname causes networking setup to fail Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] networkd fails to bring up networking on systems with long hostname [test case] setting the hostname: $ sudo hostnamectl set-hostname asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf then reboot and check the networking. [regression potential] as this adjusts logging and certain error handling while performing dhcp, any regression would likely cause dhcp failure. [scope] this is fixed by upstream commit a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated commits around it), which is included starting in v240, so this is included already in Eoan and later. This is needed in Bionic and Xenial. [other info] the problem around this is that Linux sets HOST_NAME_MAX to 64, but RFC 1035 limits DNS labels to 63 characters, so any host with a max- length single-label hostname (i.e. a 64 character hostname with no dots) will be "valid" from Linux's perspective, but will violate RFC 1035 and thus systemd will consider it invalid and won't pass it to the dhcp server. Also note that a 64-character hostname that is *not* single-label (i.e. a hostname with at least 1 dot) will not cause this problem. The systemd patches continue to reject sending the invalid hostname to the dhcp server, but do not prevent networkd from finishing setting up networking. [original description] 1) ubuntu version # lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 2) package version # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.31 Candidate: 237-3ubuntu10.31 Version table: *** 237-3ubuntu10.31 500 500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 Packag es 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages 3) I expect the network to come online correctly regardless of how long the hostname is. This is what happens with both 14.0 and 19.0 (I tested the same behavior with both of them). 4) the external network interface fails to be configured and is stuck in a (pending) state as reported by networkctl status -a setting the hostname: # hostnamectl set-hostname asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf after rebooting the machine, it no longer has network access. # journalctl Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: Starting Wait for Network to be Configured... Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: eth0: Link state is up-to-date Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: eth0: found matching network '/run/systemd/network/10-netplan-eth0.network' Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: sd-netlink: callback failed: Inv
[Group.of.nepali.translators] [Bug 1839290] Re: systemd doesn't restart a service after crashes
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. Fixed in Disco with the backported v240 patch from https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
This bug was fixed in the package systemd - 229-4ubuntu21.28
---
systemd (229-4ubuntu21.28) xenial; urgency=medium
* d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657)
* d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch:
- when restarting service after failure, replace existing queued jobs
(LP: #1839290)
* d/t/storage:
- fix buggy test (LP: #1831459)
- without scsi_debug, skip test (LP: #1847816)
* d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch:
- fix resolution of IntelliMouse (LP: #1867421)
* d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch:
- allow vacuuming journal 'root' dir (LP: #1858412)
* d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch:
- do not let invalid hostname break dhcpv4 (LP: #1862232)
* d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194)
* d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch:
- do not crash if NULL passted to journal destructor (LP: #1837914)
* d/e/initramfs-tools/hooks/udev:
- Follow symlinks when finding link files to copy into initramfs
(LP: #1868892)
-- Dan Streetman Mon, 20 Apr 2020 10:17:40
-0400
** Changed in: systemd (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/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
Fix Released
Status in linux-kvm package in Ubuntu:
New
Status in systemd package in Ubuntu:
Fix Released
Status in linux-kvm source package in Xenial:
New
Status in systemd source package in Xenial:
Fix Released
Status in linux-kvm source package in Bionic:
New
Status in systemd source package in Bionic:
Fix Released
Status in linux-kvm source package in Disco:
New
Status in systemd source package in Disco:
Won't Fix
Status in linux-kvm source package in Eoan:
New
Status in systemd source package in Eoan:
Fix Released
Status in linux-kvm source package in Focal:
New
Status in systemd source package in Focal:
Fix Released
Bug description:
Note: this bug touches on multiple packages:
- autopkgtest-cloud: merge request open to install 'modules-extra' package
- systemd: update autopkgtest to skip test if scsi_debug module isn't
available (SRU template below is for this change)
- linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have
scsi_debug module built for this kernel
[SRU template for systemd]
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*'
deb which isn't installed by default, so the test always fails when
doing a reverse-dep autopkgtest using such a kernel's meta pkg.
Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
disabled entirely; for those kernels, it will never be possible to
load the scsi_debug module and the test should be skipped.
[test case]
run the 'storage' autopkgtest with a custom kernel that doesn't
provide the scsi_debug module in the standard linux-modules deb, or
check the autopkgtest.u.c history, for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
as this modifies one of the autopkgtest --setup-commands, a regression
would most likely cause immediate test failure due to failing to
install the proper linux-* debs.
For the systemd 'storage' test change, this only skips the test if the
scsi_debug module can't be loaded (and isn't already present, i.e.
loaded or built-in). Any regression potential from that is low, but
likely would involve incorrect test skips and/or missing valid
problems due to skipping the test.
[scope]
systemd in all releases needs to have its 'storage' test updated
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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 1858412] Re: systemd vacuuming does not work for remote journals
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (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/1858412 Title: systemd vacuuming does not work for remote journals Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] attempting to vacuum journals using -D with the 'root' (in journald terms) journal directory fails to perform any vacuuming. This can lead to journal files continually increasing in size and filling up the filesystem. [test case] see original description below. [regession potential] this removes a check in the code when iterating journal directories during vacuuming, so any regression would likely occur during vacuuming, possibly causing failure to vacuum. [scope] this is fixed upstream by commit c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in version 244, so this is already included in Focal. This is needed for Eoan, Bionic, and Xenial. [original description] systemd has an issue in regard to vacuuming remote journals: https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as this version still has this problem. Steps to reproduce on "Description: Ubuntu 18.04.3 LTS": root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ Would it be possible to backport this trivial patch https://github.com/systemd/systemd/pull/13924 into 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1871166] Re: lrmd crashes
This bug was fixed in the package pacemaker - 1.1.14-2ubuntu1.7 --- pacemaker (1.1.14-2ubuntu1.7) xenial; urgency=medium [ Victor Tapia ] * d/p/lp1871166/0001-Fix-libservices-prevent-use-after-free-when-freeing-.patch, d/p/lp1871166/0002-Fix-libservices-ensure-completed-ops-aren-t-on-block.patch, d/p/lp1871166/0003-Refactor-libservices-handle-in-flight-case-first-whe.patch, d/p/lp1871166/0004-Fix-libservices-properly-cancel-in-flight-systemd-up.patch, d/p/lp1871166/0005-Fix-libservices-properly-detect-in-flight-systemd-up.patch: - prevent use-after-free segfault (LP: #1871166) -- Dan Streetman Mon, 06 Apr 2020 13:37:40 -0400 ** Changed in: pacemaker (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/1871166 Title: lrmd crashes Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Xenial: Fix Released Bug description: [impact] lrmd crashes and dumps core. [test case] I can not reproduce, but it is reproducable in the specific setup of the person reporting the bug to me. [regression potential] this patches the cancel/cleanup part of the code, so regressions would likely involve possible memory leaks (instead of use-after-free segfaults), failure to correctly cancel or cleanup operations, or other failure during cancel action. [scope] this is fixed by commits: 933d46ef20591757301784773a37e06b78906584 94a4c58f675d163085a055f59fd6c3a2c9f57c43 dc36d4375c049024a6f9e4d2277a3e6444fad05b deabcc5a6aa93dadf0b20364715b559a5b9848ac b85037b75255061a41d0ec3fd9b64f271351b43e which are all included starting with version 1.1.17, and Bionic includes version 1.1.18, so this is fixed already in Bionic and later. This is needed only for Xenial. [other info] As mentioned in the test case section, I do not have a setup where I'm able to reproduce this, but I can ask the initial reporter to test and verify the fix, and they have verified a test build fixed the problem for them. Also, the upstream commits removed two symbols, which I elided from the backported patches; those symbols are still available and, while it is unlikely there were any users of those symbols outside pacemaker itself, this change should not break any possible external users. See patch 0002 header in the upload for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1871166/+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 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (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/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] Microsoft Classic IntelliMouse moves way too fast to be usable. [test case] on a bionic system, connect affected mouse and attempt to move pointer, note it moves too fast. [regression potential] as this adds a hwdb entry for a mouse using vendor/product id and name matching, any regression would likely involve incorrectly setting dpi on a different mouse than intended. [scope] fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4 which is included starting in v240, so this is already fixed in Eoan and later. This is needed only for Xenial and Bionic. [original description] Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.transl
[Group.of.nepali.translators] [Bug 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks
This bug was fixed in the package systemd - 229-4ubuntu21.28
---
systemd (229-4ubuntu21.28) xenial; urgency=medium
* d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657)
* d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch:
- when restarting service after failure, replace existing queued jobs
(LP: #1839290)
* d/t/storage:
- fix buggy test (LP: #1831459)
- without scsi_debug, skip test (LP: #1847816)
* d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch:
- fix resolution of IntelliMouse (LP: #1867421)
* d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch:
- allow vacuuming journal 'root' dir (LP: #1858412)
* d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch:
- do not let invalid hostname break dhcpv4 (LP: #1862232)
* d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194)
* d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch:
- do not crash if NULL passted to journal destructor (LP: #1837914)
* d/e/initramfs-tools/hooks/udev:
- Follow symlinks when finding link files to copy into initramfs
(LP: #1868892)
-- Dan Streetman Mon, 20 Apr 2020 10:17:40
-0400
** Changed in: systemd (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/1868892
Title:
initramfs-tools/hooks/udev for network *.link really sucks
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Eoan:
Fix Released
Status in systemd source package in Focal:
In Progress
Bug description:
[impact]
If the /{etc,lib}/systemd/network directory itself is a symlink, the find
command will not actually find any of the files in the dir it links to.
[test case]
$ sudo touch /etc/systemd/network/lp1868892.link
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
...
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
usr/lib/systemd/network/lp1868892.link
$ sudo mv /etc/systemd/network /etc/systemd/network.abc
$ sudo ln -s network.abc /etc/systemd/network
$ sudo update-initramfs -u
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
$
[regression potential]
this adjusts how link files are included in the initramfs, so
regressions would likely occur when creating new initramfs, such as
failure to create initramfs at all, or failure to properly copy link
files into the initramfs, causing network setup failure.
[scope]
this is a Debian/Ubuntu specific file, and the Debian MR was just
opened, so this is needed for Debian and all releases of Ubuntu.
[other info]
This bug likely has a very limited impact, as it is uncommon to
symlink either the /lib/systemd/network or /etc/systemd/network dirs.
[original description]
If one creates e.g. /etc/systemd/network.cu and
/etc/systemd/network.fc and symlinks /etc/systemd/network to one of
them, network setup will fail on reboot, because /usr/share/initramfs-
tools/hooks/udev does a very poor job: it simply checks for a
directory instead of the link files and therefore skips copying
required files to the ram image. Another poor job is done when copying
the files to the ram image: instead of following symlinks it copies
them as which in turn makes them useless, because it does not copy the
related dirs and thus the symlinks point to nothing. So keeping the
system in an consistent state which such poor scripts is very hard,
asking for trouble.
Suggested fix is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1870194] Re: systemd-fsckd autopkgtest always fails on arm64
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (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/1870194 Title: systemd-fsckd autopkgtest always fails on arm64 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] the autopkgtest arm64 instances fail to reboot and always fail the test [test case] check autopkgtest results for arm64 instances, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz [regression potential] these tests have never successfully run on arm64, so skipping them on arm64 should have almost no regression potential; any regression would likely involve incorrectly failed test or not-run tests. [scope] this test is already skipped on arm64 starting on Eoan. This is needed only for Xenial and Bionic. [other info] related is bug 1748280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870194/+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 1837914] Re: restart systemd-jounald fails
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (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/1837914 Title: restart systemd-jounald fails Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: [impact] in some situations, restarting journald causes assertion failure. [test case] intermittently, when restarting journald. See upstream bug for repro details. [regression potential] this adjusts the journal file destructor, so any regression would likely occur when cleaning up journal files and/or stopping/restarting. [scope] this is fixed by commit c377a6f3ad3d9bed4ce7e873e8e9ec6b1650c57d which is included in Focal. This is needed for Eoan and earlier. [original description] While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal /journal-file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837914/+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 1839290] Re: systemd doesn't restart a service after crashes
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. Fixed in Disco with the backported v240 patch from https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+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 1862232] Re: Long hostname causes networking setup to fail
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (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/1862232 Title: Long hostname causes networking setup to fail Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] networkd fails to bring up networking on systems with long hostname [test case] setting the hostname: $ sudo hostnamectl set-hostname asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf then reboot and check the networking. [regression potential] as this adjusts logging and certain error handling while performing dhcp, any regression would likely cause dhcp failure. [scope] this is fixed by upstream commit a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated commits around it), which is included starting in v240, so this is included already in Eoan and later. This is needed in Bionic and Xenial. [other info] the problem around this is that Linux sets HOST_NAME_MAX to 64, but RFC 1035 limits DNS labels to 63 characters, so any host with a max- length single-label hostname (i.e. a 64 character hostname with no dots) will be "valid" from Linux's perspective, but will violate RFC 1035 and thus systemd will consider it invalid and won't pass it to the dhcp server. Also note that a 64-character hostname that is *not* single-label (i.e. a hostname with at least 1 dot) will not cause this problem. The systemd patches continue to reject sending the invalid hostname to the dhcp server, but do not prevent networkd from finishing setting up networking. [original description] 1) ubuntu version # lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 2) package version # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.31 Candidate: 237-3ubuntu10.31 Version table: *** 237-3ubuntu10.31 500 500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 Packag es 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages 3) I expect the network to come online correctly regardless of how long the hostname is. This is what happens with both 14.0 and 19.0 (I tested the same behavior with both of them). 4) the external network interface fails to be configured and is stuck in a (pending) state as reported by networkctl status -a setting the hostname: # hostnamectl set-hostname asdfasdfasdfasdfasdfasdfasdfasdfasdfasd
[Group.of.nepali.translators] [Bug 1858412] Re: systemd vacuuming does not work for remote journals
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (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/1858412 Title: systemd vacuuming does not work for remote journals Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] attempting to vacuum journals using -D with the 'root' (in journald terms) journal directory fails to perform any vacuuming. This can lead to journal files continually increasing in size and filling up the filesystem. [test case] see original description below. [regession potential] this removes a check in the code when iterating journal directories during vacuuming, so any regression would likely occur during vacuuming, possibly causing failure to vacuum. [scope] this is fixed upstream by commit c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in version 244, so this is already included in Focal. This is needed for Eoan, Bionic, and Xenial. [original description] systemd has an issue in regard to vacuuming remote journals: https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as this version still has this problem. Steps to reproduce on "Description: Ubuntu 18.04.3 LTS": root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ Would it be possible to backport this trivial patch https://github.com/systemd/systemd/pull/13924 into 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (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/1870811 Title: compile auto test failure, and root-unittest failure, is extremely noisy Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build, e.g. https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+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 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks
This bug was fixed in the package systemd - 237-3ubuntu10.40
---
systemd (237-3ubuntu10.40) bionic; urgency=medium
* d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657)
* d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch:
- when restarting service after failure, replace existing queued jobs
(LP: #1839290)
* d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch:
- fix resolution of IntelliMouse (LP: #1867421)
* d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch:
- allow vacuuming journal 'root' dir (LP: #1858412)
*
d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch,
d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch,
d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch,
d/p/lp1862232/0004-network-use-free_and_replace.patch,
d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch,
d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch,
d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch:
- do not fail network setup if hostname is not valid (LP: #1862232)
* d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194)
* d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch:
- fix test-seccomp failure (LP: #1870589)
* d/rules: use meson --print-errorlogs instead of cat testlog
- (LP: #1870811)
* d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch:
- sync journal before reading from it (LP: #1776654)
* d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch:
- do not crash if NULL passted to journal destructor (LP: #1837914)
* d/e/initramfs-tools/hooks/udev:
- Follow symlinks when finding link files to copy into initramfs
(LP: #1868892)
-- Dan Streetman Mon, 20 Apr 2020 10:12:49
-0400
** Changed in: systemd (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/1868892
Title:
initramfs-tools/hooks/udev for network *.link really sucks
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Eoan:
Fix Released
Status in systemd source package in Focal:
In Progress
Bug description:
[impact]
If the /{etc,lib}/systemd/network directory itself is a symlink, the find
command will not actually find any of the files in the dir it links to.
[test case]
$ sudo touch /etc/systemd/network/lp1868892.link
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
...
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
usr/lib/systemd/network/lp1868892.link
$ sudo mv /etc/systemd/network /etc/systemd/network.abc
$ sudo ln -s network.abc /etc/systemd/network
$ sudo update-initramfs -u
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
$
[regression potential]
this adjusts how link files are included in the initramfs, so
regressions would likely occur when creating new initramfs, such as
failure to create initramfs at all, or failure to properly copy link
files into the initramfs, causing network setup failure.
[scope]
this is a Debian/Ubuntu specific file, and the Debian MR was just
opened, so this is needed for Debian and all releases of Ubuntu.
[other info]
This bug likely has a very limited impact, as it is uncommon to
symlink either the /lib/systemd/network or /etc/systemd/network dirs.
[original description]
If one creates e.g. /etc/systemd/network.cu and
/etc/systemd/network.fc and symlinks /etc/systemd/network to one of
them, network setup will fail on reboot, because /usr/share/initramfs-
tools/hooks/udev does a very poor job: it simply checks for a
directory instead of the link files and therefore skips copying
required files to the ram image. Another poor job is done when copying
the files to the ram image: instead of following symlinks it copies
them as which in turn makes them useless, because it does not copy the
related dirs and thus the symlinks point to nothing. So keeping the
system in an consistent state which such poor scripts is very hard,
asking for trouble.
Suggested fix is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~gro
[Group.of.nepali.translators] [Bug 1874776] Re: xenial/linux-gcp: 4.15.0-1071.81~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => 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: 1874777 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Monday, 11. May 2020 13:31 UTC + phase: Building in ppa + phase-changed: Monday, 11. May 2020 15:10 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded - prepare-package-signed: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building + meta:building trackers: xenial/linux-gcp/gcp-kernel: bug 1874774 xenial/linux-gcp/gke-kernel: bug 1874775 variant: debs + versions: + main: 4.15.0-1071.81~16.04.1 + meta: 4.15.0.1071.77 + signed: 4.15.0-1071.81~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/1874776 Title: xenial/linux-gcp: 4.15.0-1071.81~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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 verification-testing series: New Status in linux-gcp 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 -- kernel-stable-master-bug: 1874777 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Building in ppa phase-changed: Monday, 11. May 2020 15:10 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building meta:building trackers: xenial/linux-gcp/gcp-kernel: bug 1874774 xenial/linux-gcp/gke-kernel: bug 1874775 variant: debs versions: main: 4.15.0-1071.81~16.04.1 meta: 4.15.0.1071.77 signed: 4.15.0-1071.81~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1874776/+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 1862657] Re: systemd autopkgtest 'logind' fails when running with linux-kvm
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (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/1862657 Title: systemd autopkgtest 'logind' fails when running with linux-kvm Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] the logind autopkgtest tries to access /sys/power/state, but because linux-kvm has CONFIG_PM unset, there is no /sys/power/state file [test case] check autopkgtest, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz autopkgtest [13:48:53]: test logind: ---] autopkgtest [13:48:53]: test logind: - - - - - - - - - - results - - - - - - - - - - logind FAIL stderr: grep: /sys/power/state: No such file or directory autopkgtest [13:48:53]: test logind: - - - - - - - - - - stderr - - - - - - - - - - grep: /sys/power/state: No such file or directory [regression potential] regressions would likely involve incorrectly skipped logind test. [scope] this fails for all releases; Xenial, Bionic, Eoan, and Focal. [other info] it's unclear if linux-kvm should have CONFIG_PM (and other config) enabled or not. However, it's not the intention of systemd's autopkgtests to look for missing config in the kernel; the test already skips if 'mem' isn't in /sys/power/state, so it should also skip if /sys/power/state isn't present at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862657/+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 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (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/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] Microsoft Classic IntelliMouse moves way too fast to be usable. [test case] on a bionic system, connect affected mouse and attempt to move pointer, note it moves too fast. [regression potential] as this adds a hwdb entry for a mouse using vendor/product id and name matching, any regression would likely involve incorrectly setting dpi on a different mouse than intended. [scope] fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4 which is included starting in v240, so this is already fixed in Eoan and later. This is needed only for Xenial and Bionic. [original description] Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.boar
[Group.of.nepali.translators] [Bug 1870194] Re: systemd-fsckd autopkgtest always fails on arm64
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (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/1870194 Title: systemd-fsckd autopkgtest always fails on arm64 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] the autopkgtest arm64 instances fail to reboot and always fail the test [test case] check autopkgtest results for arm64 instances, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz [regression potential] these tests have never successfully run on arm64, so skipping them on arm64 should have almost no regression potential; any regression would likely involve incorrectly failed test or not-run tests. [scope] this test is already skipped on arm64 starting on Eoan. This is needed only for Xenial and Bionic. [other info] related is bug 1748280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870194/+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 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy
This bug was fixed in the package systemd - 242-7ubuntu3.8 --- systemd (242-7ubuntu3.8) eoan; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1859862-network-Do-not-disable-IPv6-by-writing-to-sysctl.patch: - enable ipv6 when needed (LP: #1859862) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 09:44:51 -0400 ** Changed in: systemd (Ubuntu Eoan) 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/1870811 Title: compile auto test failure, and root-unittest failure, is extremely noisy Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build, e.g. https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+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 1862657] Re: systemd autopkgtest 'logind' fails when running with linux-kvm
This bug was fixed in the package systemd - 242-7ubuntu3.8 --- systemd (242-7ubuntu3.8) eoan; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1859862-network-Do-not-disable-IPv6-by-writing-to-sysctl.patch: - enable ipv6 when needed (LP: #1859862) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 09:44:51 -0400 ** Changed in: systemd (Ubuntu Eoan) 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/1862657 Title: systemd autopkgtest 'logind' fails when running with linux-kvm Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] the logind autopkgtest tries to access /sys/power/state, but because linux-kvm has CONFIG_PM unset, there is no /sys/power/state file [test case] check autopkgtest, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz autopkgtest [13:48:53]: test logind: ---] autopkgtest [13:48:53]: test logind: - - - - - - - - - - results - - - - - - - - - - logind FAIL stderr: grep: /sys/power/state: No such file or directory autopkgtest [13:48:53]: test logind: - - - - - - - - - - stderr - - - - - - - - - - grep: /sys/power/state: No such file or directory [regression potential] regressions would likely involve incorrectly skipped logind test. [scope] this fails for all releases; Xenial, Bionic, Eoan, and Focal. [other info] it's unclear if linux-kvm should have CONFIG_PM (and other config) enabled or not. However, it's not the intention of systemd's autopkgtests to look for missing config in the kernel; the test already skips if 'mem' isn't in /sys/power/state, so it should also skip if /sys/power/state isn't present at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862657/+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 1837914] Re: restart systemd-jounald fails
This bug was fixed in the package systemd - 242-7ubuntu3.8 --- systemd (242-7ubuntu3.8) eoan; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1859862-network-Do-not-disable-IPv6-by-writing-to-sysctl.patch: - enable ipv6 when needed (LP: #1859862) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 09:44:51 -0400 ** Changed in: systemd (Ubuntu Eoan) 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/1837914 Title: restart systemd-jounald fails Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] in some situations, restarting journald causes assertion failure. [test case] intermittently, when restarting journald. See upstream bug for repro details. [regression potential] this adjusts the journal file destructor, so any regression would likely occur when cleaning up journal files and/or stopping/restarting. [scope] this is fixed by commit c377a6f3ad3d9bed4ce7e873e8e9ec6b1650c57d which is included in Focal. This is needed for Eoan and earlier. [original description] While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal /journal-file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837914/+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 1858412] Re: systemd vacuuming does not work for remote journals
This bug was fixed in the package systemd - 242-7ubuntu3.8 --- systemd (242-7ubuntu3.8) eoan; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1859862-network-Do-not-disable-IPv6-by-writing-to-sysctl.patch: - enable ipv6 when needed (LP: #1859862) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 09:44:51 -0400 ** Changed in: systemd (Ubuntu Eoan) 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/1858412 Title: systemd vacuuming does not work for remote journals Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] attempting to vacuum journals using -D with the 'root' (in journald terms) journal directory fails to perform any vacuuming. This can lead to journal files continually increasing in size and filling up the filesystem. [test case] see original description below. [regession potential] this removes a check in the code when iterating journal directories during vacuuming, so any regression would likely occur during vacuuming, possibly causing failure to vacuum. [scope] this is fixed upstream by commit c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in version 244, so this is already included in Focal. This is needed for Eoan, Bionic, and Xenial. [original description] systemd has an issue in regard to vacuuming remote journals: https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as this version still has this problem. Steps to reproduce on "Description: Ubuntu 18.04.3 LTS": root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ Would it be possible to backport this trivial patch https://github.com/systemd/systemd/pull/13924 into 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks
This bug was fixed in the package systemd - 242-7ubuntu3.8
---
systemd (242-7ubuntu3.8) eoan; urgency=medium
* d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657)
* d/p/lp1859862-network-Do-not-disable-IPv6-by-writing-to-sysctl.patch:
- enable ipv6 when needed (LP: #1859862)
* d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch:
- allow vacuuming journal 'root' dir (LP: #1858412)
* d/rules: use meson --print-errorlogs instead of cat testlog
- (LP: #1870811)
* d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch:
- sync journal before reading from it (LP: #1776654)
* d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch:
- do not crash if NULL passted to journal destructor (LP: #1837914)
* d/e/initramfs-tools/hooks/udev:
- Follow symlinks when finding link files to copy into initramfs
(LP: #1868892)
-- Dan Streetman Mon, 20 Apr 2020 09:44:51
-0400
** Changed in: systemd (Ubuntu Eoan)
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/1868892
Title:
initramfs-tools/hooks/udev for network *.link really sucks
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Eoan:
Fix Released
Status in systemd source package in Focal:
In Progress
Bug description:
[impact]
If the /{etc,lib}/systemd/network directory itself is a symlink, the find
command will not actually find any of the files in the dir it links to.
[test case]
$ sudo touch /etc/systemd/network/lp1868892.link
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
...
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
usr/lib/systemd/network/lp1868892.link
$ sudo mv /etc/systemd/network /etc/systemd/network.abc
$ sudo ln -s network.abc /etc/systemd/network
$ sudo update-initramfs -u
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
$
[regression potential]
this adjusts how link files are included in the initramfs, so
regressions would likely occur when creating new initramfs, such as
failure to create initramfs at all, or failure to properly copy link
files into the initramfs, causing network setup failure.
[scope]
this is a Debian/Ubuntu specific file, and the Debian MR was just
opened, so this is needed for Debian and all releases of Ubuntu.
[other info]
This bug likely has a very limited impact, as it is uncommon to
symlink either the /lib/systemd/network or /etc/systemd/network dirs.
[original description]
If one creates e.g. /etc/systemd/network.cu and
/etc/systemd/network.fc and symlinks /etc/systemd/network to one of
them, network setup will fail on reboot, because /usr/share/initramfs-
tools/hooks/udev does a very poor job: it simply checks for a
directory instead of the link files and therefore skips copying
required files to the ram image. Another poor job is done when copying
the files to the ram image: instead of following symlinks it copies
them as which in turn makes them useless, because it does not copy the
related dirs and thus the symlinks point to nothing. So keeping the
system in an consistent state which such poor scripts is very hard,
asking for trouble.
Suggested fix is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
Yeah Dan, thanks for chiming in. In particular that would be at least (but not lmited to) the changes: 8.04 Rework DTLS MTU detection. (#10) 7.08 Support automatic DTLS MTU detection with OpenSSL. 7.07 Automatic DTLS MTU detection. Ubuntu has these newer versions. Bionic 18.04 is on 7.08 and the most recent LTS Focal is at 8.05. The current development release is at the latest 8.09 of openconnect. These are new features added in 7.07 and 7.08 - IMHO they do not qualify for a SRU release into Xenial [1] - especially since you can "get away" with a config change that mitigates the issue. [1]: https://wiki.ubuntu.com/StableReleaseUpdates ** Also affects: openssh (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openconnect (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: openssh (Ubuntu Xenial) ** Changed in: openssh (Ubuntu) Status: Confirmed => Invalid ** Changed in: openconnect (Ubuntu Xenial) Status: New => Confirmed ** Changed in: openconnect (Ubuntu) Status: Confirmed => Fix Released ** Changed in: openconnect (Ubuntu Xenial) Importance: Undecided => Wishlist -- 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/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Invalid Status in openconnect package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Invalid Status in openconnect source package in Xenial: Confirmed Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algori
[Group.of.nepali.translators] [Bug 1877981] Re: xenial/linux-hwe: 4.15.0-101.102~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => 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: 1877262 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Packaging - phase-changed: Monday, 11. May 2020 10:47 UTC + phase: Building in ppa + phase-changed: Monday, 11. May 2020 11:49 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded - prepare-package-signed: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building replaces: bug 1874787 variant: debs + versions: + main: 4.15.0-101.102~16.04.1 + meta: 4.15.0.101.108 + signed: 4.15.0-101.102~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/1877981 Title: xenial/linux-hwe: 4.15.0-101.102~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-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 -- kernel-stable-master-bug: 1877262 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Building in ppa phase-changed: Monday, 11. May 2020 11:49 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building replaces: bug 1874787 variant: debs versions: main: 4.15.0-101.102~16.04.1 meta: 4.15.0.101.108 signed: 4.15.0-101.102~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1877981/+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
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/RDBBHxWy/388-xenial-hwe-linux- image-4150-100-generic-4150-10010116041 ** Changed in: kernel-sru-workflow/certification-testing 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/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: Fix Released 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: Fix Released 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 security-signoff: Stalled -- 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 1874804] Re: xenial/linux: 4.4.0-179.209 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/vgS6buv9/365-xenial-linux- image-440-179-generic-440-179209 ** Changed in: kernel-sru-workflow/certification-testing 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/1874804 Title: xenial/linux: 4.4.0-179.209 -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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 29. April 2020 23:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1874802 trusty/linux-lts-xenial: bug 1874803 xenial/linux-aws: bug 1874793 xenial/linux-cascade: bug 1874795 xenial/linux-fips: bug 1874801 xenial/linux-kvm: bug 1874796 xenial/linux-raspi2: bug 1874798 xenial/linux-snapdragon: bug 1874800 xenial/linux/caracalla-kernel: bug 1874789 xenial/linux/pc-kernel: bug 1874790 xenial/linux/stlouis-kernel: bug 1874791 variant: debs versions: main: 4.4.0-179.209 meta: 4.4.0.179.187 signed: 4.4.0-179.209 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1874804/+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 1413379] Re: boinc doesn't always detect Virtualbox
Since >=7.9.3 is mentioned to be good this seems only to still affect Xenial. ** Also affects: boinc (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: boinc (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/1413379 Title: boinc doesn't always detect Virtualbox Status in Boinc: Fix Released Status in boinc package in Ubuntu: Fix Released Status in boinc source package in Xenial: New Bug description: The BOINC client does not always successfully detect Virtualbox, though Virtualbox does start successfully each time. 15-Jan-2015 12:53:29 [---] VirtualBox version: 4.3.20r96996 16-Jan-2015 11:26:36 [---] VirtualBox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module 17-Jan-2015 13:31:43 [---] VirtualBox version: 4.3.20r96996 18-Jan-2015 09:41:57 [---] VirtualBox version: 4.3.20r96996 18-Jan-2015 22:43:25 [---] VirtualBox version: 4.3.20r96996 19-Jan-2015 14:40:57 [---] VirtualBox version: 4.3.20r96996 19-Jan-2015 20:45:52 [---] VirtualBox version: 4.3.20r96996 19-Jan-2015 21:38:36 [---] VirtualBox version: 4.3.20r96996 19-Jan-2015 22:27:01 [---] VirtualBox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module 20-Jan-2015 00:42:59 [---] VirtualBox version: 4.3.20r96996 20-Jan-2015 14:23:18 [---] VirtualBox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module 20-Jan-2015 21:25:13 [---] VirtualBox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module 20-Jan-2015 22:24:35 [---] VirtualBox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module 20-Jan-2015 23:01:51 [---] VirtualBox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module 20-Jan-2015 23:12:46 [---] VirtualBox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module 21-Jan-2015 12:59:39 [---] VirtualBox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module 21-Jan-2015 13:21:59 [---] VirtualBox version: 4.3.20r96996 21-Jan-2015 20:01:22 [---] VirtualBox version: 4.3.20r96996 21-Jan-2015 20:10:16 [---] VirtualBox version: 4.3.20r96996 To work around I changed the start sequence of the init script: # mv 20boinc-client 80boinc-client It would appear that boinc starts too early in the boot sequence. $ cd /etc/rc2.d $ ls S* S01policykit S20hotkey-setup S20winbind S50rsync S99acpi-support S10apmd S20kerneloops S24dhcdbd S70dns-clean S99grub-common S20clamav-daemon S20nbd-server S35vboxautostart-service S70pppd-dns S99ondemand S20clamav-freshclam S20openbsd-inetd S35vboxballoonctrl-service S75sudo S99rc.local S20fancontrolS20speech-dispatcher S35vboxweb-service S80boinc-client S20hddtemp S20vboxdrvS50pulseaudio S95distcc To manage notifications about this bug go to: https://bugs.launchpad.net/boinc-upstream/+bug/1413379/+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 1873448] Re: stress-ng in xenial segfaults on dup stressor on arm64
** Changed in: stress-ng (Ubuntu Xenial)
Status: In Progress => Fix Released
** Changed in: stress-ng (Ubuntu Xenial)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1873448
Title:
stress-ng in xenial segfaults on dup stressor on arm64
Status in stress-ng package in Ubuntu:
New
Status in stress-ng source package in Xenial:
Fix Committed
Bug description:
== SRU justification, Xenial ==
When running the --dup stressor with stress-ng with a process that is
allowed to open more than 64K file descriptors we trigger a segfault
because of an array overflow.
== Fix ==
A simple fix is required, just a bounds check on the maximum size
max_fd to limit it to the size of the fds array.
== Testcase ==
stress-ng on arm64 with the --dup stressor will trigger this quite
easily. The bug was found during regression testing of the previous
xenial stress-ng upload.
stress-ng --dup
without the fix this will segfault. with the fix it works correctly.
== Regression Potential ==
Low. This affects one stress case in stress-ng, the fix is localized
and it a backport from an upstream stress-ng fix that has been working
for several years w/o problem.
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
stress-ng: info: [10979] defaulting to a 86400 second run per stressor
stress-ng: info: [10979] dispatching hogs: 1 dup
stress-ng: info: [10979] cache allocate: using built-in defaults as unable
to determine cache details
stress-ng: info: [10979] cache allocate: default cache size: 2048K
[New process 10982]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
65536 1048573
Thread 2.1 "stress-ng-dup" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7ff1000 (LWP 10982)]
0x004191f0 in stress_dup (counter=0xb7cbee78, instance=, max_ops=0, name=)
at stress-dup.c:63
63fds[i] = dup(fds[0]);
This requires a fix from commit:
67d872611b860a79b03dca8c7549e5cee7fec4eb Mon Sep 17 00:00:00 2001
From: Colin Ian King
Date: Tue, 8 Nov 2016 15:50:20 +
Subject: [PATCH] treewide: remove messy #if defined() build checks
diff --git a/stress-dup.c b/stress-dup.c
index 2fe2d6a6..0ac13fee 100644
--- a/stress-dup.c
+++ b/stress-dup.c
@@ -45,7 +45,7 @@ int stress_dup(
const char *name)
{
int fds[STRESS_FD_MAX];
- const size_t max_fd = stress_get_file_limit();
+ size_t max_fd = stress_get_file_limit();
size_t i;
#if defined(__linux__)
bool do_dup3 = true;
@@ -53,6 +53,9 @@ int stress_dup(
(void)instance;
+ if (max_fd > SIZEOF_ARRAY(fds))
+ max_fd = SIZEOF_ARRAY(fds);
+
fds[0] = open("/dev/zero", O_RDONLY);
if (fds[0] < 0) {
pr_fail_dbg(name, "open on /dev/zero");
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1873448/+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
