[Group.of.nepali.translators] [Bug 1775165] Re: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel
I have gone ahead and backported the fixes for xenial's 4.4 kernel. This patch series is for ubuntu-xenial 4.4: https://paste.ubuntu.com/p/Kj43J6H3Hm/ This patch series is for vanilla upstream 4.4: https://paste.ubuntu.com/p/MzdjcHCqbz/ Both patch and compile and fix the problem. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Tags added: sts ** Description changed: - The "fanotify07" and "fanotify08" from the LTP syscall tests has failed - on a testing node with Trusty kernel installed. + BugLink: https://bugs.launchpad.net/bugs/1775165 + + [Impact] + + When userspace tasks which are processing fanotify permission events act + incorrectly, the fsnotify_mark_srcu SRCU is held indefinitely which causes + the whole notification subsystem to hang. + + This has been seen in production, and it can also be seen when running the + Linux Test Project testsuite, specifically fanotify07. + + [Fix] + + Instead of holding the SRCU lock while waiting for userspace to respond, + which may never happen, or not in the order we are expecting, we drop the + fsnotify_mark_srcu SRCU lock before waiting for userspace response, and then + reacquire the lock again when userspace responds. + + The fixes are from a series of upstream commits: + + 05f0e38724e8449184acd8fbf0473ee5a07adc6c (cherry-pick) + 9385a84d7e1f658bb2d96ab798393e4b16268aaa (backport) + abc77577a669f424c5d0c185b9994f2621c52aa4 (backport) + + The following are upstream commits necessary for the fixes to function: + + 35e481761cdc688dbee0ef552a13f49af8eba6cc (backport) + 0918f1c309b86301605650c836ddd2021d311ae2 (cherry-pick) + + [Testcase] + + You can reproduce the problem pretty quickly with the Linux Test + Project: Steps (with root): - 1. sudo apt-get install git xfsprogs -y - 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git - 3. cd ltp - 4. make autotools - 5. ./configure - 6. make; make install - 7. cd /opt/ltp - 8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs - 9. ./runltp -f /tmp/jobs + 1. sudo apt-get install git xfsprogs -y + 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git + 3. cd ltp + 4. make autotools + 5. ./configure + 6. make; make install + 7. cd /opt/ltp + 8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs + 9. ./runltp -f /tmp/jobs + + On a stock Xenial kernel, the system will hang, and the testcase will look like: <<>> - tag=fanotify07 stime=1528197132 - cmdline="fanotify07" + tag=fanotify07 stime=1554326200 + cmdline="fanotify07 " contacts="" analysis=exit <<>> - incrementing stop - tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s + tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... <<>> initiation_status="ok" duration=350 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> - INFO: ltp-pan reported some tests FAIL - LTP Version: 20180515 - [ 841.063676] INFO: task fanotify07:3660 blocked for more than 120 seconds. - [ 841.063692] Not tainted 3.13.0-149-generic #199-Ubuntu - [ 841.063705] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. - [ 841.063723] fanotify07 D 8804584742f0 0 3660 3652 0x - [ 841.063724] 880459e9bd00 0086 88045556b000 00013b00 - [ 841.063726] 880459e9bfd8 00013b00 88045556b000 880459b4e690 - [ 841.063728] 880458474200 8804584742f0 0002 - [ 841.063730] Call Trace: - [ 841.063731] [] schedule+0x29/0x70 - [ 841.063733] [] fanotify_handle_event+0x110/0x1d0 - [ 841.063735] [] ? prepare_to_wait_event+0x100/0x100 - [ 841.063737] [] send_to_group+0x166/0x240 - [ 841.063738] [] ? touch_atime+0x71/0x140 - [ 841.063740] [] fsnotify+0x2e5/0x320 - [ 841.063742] [] security_file_permission+0x94/0xb0 - [ 841.063743] [] rw_verify_area+0x52/0xd0 - [ 841.063745] [] vfs_read+0x6a/0x160 - [ 841.063746] [] SyS_read+0x49/0xa0 - [ 841.063748] [] system_call_fastpath+0x1a/0x1f - [ 1304.848642] ltp-pan[3809]: segfault at 0 ip 7f07c8aafdfa sp 7ffc1da92078 error 4 in libc-2.19.so[7f07c8a27000+1be000] + Looking at
[Group.of.nepali.translators] [Bug 1822828] Re: linux-raspi2: 4.4.0-1107.115 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822834 - phase: Ready for Packaging - phase-changed: Wednesday, 03. April 2019 09:35 UTC + phase: Packaging + phase-changed: Tuesday, 09. April 2019 23:09 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822828 Title: linux-raspi2: 4.4.0-1107.115 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1822834 phase: Packaging phase-changed: Tuesday, 09. April 2019 23:09 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822828/+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 1824016] Re: Built-Using incorrect
** Changed in: linux-signed-hwe (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-signed-hwe (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-signed-hwe-edge (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-signed-hwe-edge (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-signed (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-signed (Ubuntu Xenial) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-signed (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-signed (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-signed (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux-signed (Ubuntu Cosmic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-signed (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-signed (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-signed-hwe (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-signed-hwe (Ubuntu Xenial) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-signed-hwe (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-signed-hwe (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-signed-hwe-edge (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-signed-hwe-edge (Ubuntu Xenial) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux-signed-hwe-edge (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-signed-hwe-edge (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Description changed: [Impact] The Build-Using control file field is incorrect for linux-signed-hwe & linux-signed-hwe-edge. They claim they were built against the "linux" package, but should be linux-hwe/linux-hwe-edge respectively. [Test Case] Look at the Packages file. [Fix] Detect and insert the correct package name at build time. [Regression Risk] + Hm.. maybe if something gets added using the PACKAGE keyword in control.stub that isn't intended to be replaced gets accidentally replaced, screwing up some other control field? -- 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/1824016 Title: Built-Using incorrect Status in linux-signed package in Ubuntu: In Progress Status in linux-signed-hwe package in Ubuntu: Invalid Status in linux-signed-hwe-edge package in Ubuntu: Invalid Status in linux-signed source package in Xenial: In Progress Status in linux-signed-hwe source package in Xenial: In Progress Status in linux-signed-hwe-edge source package in Xenial: In Progress Status in linux-signed source package in Bionic: In Progress Status in linux-signed-hwe source package in Bionic: In Progress Status in linux-signed-hwe-edge source package in Bionic: In Progress Status in linux-signed source package in Cosmic: In Progress Status in linux-signed-hwe source package in Cosmic: Invalid Status in linux-signed-hwe-edge source package in Cosmic: Invalid Status in linux-signed source package in Disco: In Progress Status in linux-signed-hwe source package in Disco: Invalid Status in linux-signed-hwe-edge source package in Disco: Invalid Bug description: [Impact] The Build-Using control file field is incorrect for linux-signed-hwe & linux-signed-hwe-edge. They claim they were built against the "linux" package, but should be linux-hwe/linux-hwe-edge respectively. [Test Case] Look at the Packages file. [Fix] Detect and insert the correct package name at build time. [Regression Risk] Hm.. maybe if something gets added using the PACKAGE keyword in control.stub that isn't intended to be replaced gets accidentally replaced, screwing up some other control field? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1824016/+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 1822834] Re: linux: 4.4.0-146.172 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/h1os3Oiy/909-pc-kernel-440-146172-206 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822834 Title: linux: 4.4.0-146.172 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid 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 backports: bug 1822832 (trusty/linux-aws), bug 1822833 (trusty/linux-lts-xenial) derivatives: bug 1822824 (linux-aws), bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap pc-kernel not in expected channel(s): amd64:latest/candidate i386:latest/candidate' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+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 1401532] Re: GRUB's Secure Boot implementation loads unsigned kernel without warning
This bug was fixed in the package grub2 - 2.02~beta2-9ubuntu1.17 --- grub2 (2.02~beta2-9ubuntu1.17) trusty; urgency=medium * debian/grub-check-signatures: check kernel signatures against keys known in firmware, in case a kernel is signed but not using a key that will pass validation, such as when using kernels coming from a PPA. (LP: #1789918) * debian/patches/linuxefi_disable_sb_fallback.patch: Disallow unsigned kernels if UEFI Secure Boot is enabled. If UEFI Secure Boot is enabled and kernel signature verification fails, do not boot the kernel. Patch from Linn Crosetto. (LP: #1401532) -- Mathieu Trudel-Lapierre Fri, 22 Mar 2019 11:36:54 -0400 ** Changed in: grub2 (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: grub2-signed (Ubuntu Trusty) 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/1401532 Title: GRUB's Secure Boot implementation loads unsigned kernel without warning Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in grub2 source package in Trusty: Fix Released Status in grub2-signed source package in Trusty: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in grub2 source package in Bionic: Fix Released Status in grub2-signed source package in Bionic: Fix Released Bug description: [Rationale] GRUB should help us enforce that in UEFI mode, only signed kernels are loaded. It should not silently fall back to loading unsigned kernels. [Impact] All our users booting in UEFI; on all supported releases. [Test cases] = grub2 = Booting unsigned kernels: 1) Try to boot a custom kernel 2) Verify that the kernel will not be loaded by grub (you should see an error message about the signature) Booting signed kernels: 1) Try to boot an official signed kernel (from -release or -updates) 2) Verify that the system boots normally and no warnings are shown about signature. [Regression Potential] Any failure to boot presenting as a failure to load the kernel from within grub, with an "invalid signature" type error message or not, should be investigated as a potential regression of this stable update. --- Me and some other students have conducted some various experiments on Secure Boot enabled machines. The main focus of the tests was to circumvent Secure Boot and load unsigned kernels or kernels that have been signed with other keys. On your SecureBoot (https://wiki.ubuntu.com/SecurityTeam/SecureBoot) it is outlined that GRUB will boot unsigned kernels when the kernel is unsigned. During one of our experiments it seemed that this statement was true and that GRUB loads unsigned kernels as described on your page. We understand that for various reasons GRUB should still support the use-case when an unsigned kernel must be loaded, but with the current approach the user isn't aware if there is a whole chain of trust. For example, it could still be possible to load some malware before it boots the Operating System itself (bootkits). One of the many reasons that Secure Boot has been developed is to protect the user from these kind of attacks. With the current approach the purpose of Secure Boot is somewhat defeated, and the user doesn't know if the whole chain has been verified or not. It could easily be the case that an unsigned kernel has been loaded by Ubuntu without the user noticing. From our point of view, a better approach would be to inform the user that an unsigned kernel will be loaded and that the user can make a choice if he/she wants to proceed. The default action could be to accept the option, remember the user's option and sometimes remind the user of the fact that it is loading an unsigned kernel. This problem is of course related to GRUB itself and not to Ubuntu itself. The reason for filing this bug and informing the SecurityTeam of Ubuntu is to ask for their opinions and what your point of view is on the current approach and to see if other users classify this as a "bug". GRUB2 versions: grub-2.02~beta2, 1.34.1+2.02~beta2-9ubuntu1 Ubuntu version: Trusty (will also affect newer and older versions, GRUB specific problem) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1401532/+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 1793298] Re: snapd-glib changes needed for pulseaudio snap policy module xenial backport
This bug was fixed in the package snapd-glib - 1.47-0ubuntu0.16.04.0 --- snapd-glib (1.47-0ubuntu0.16.04.0) xenial; urgency=medium * New upstream release (LP: #1818766) * debian/rules: - Build with --enable-installed-tests * debian/tests/control: * debian/tests/unit: * debian/snapd-glib-tests.install: - Add autopkg tests * debian/libsnapd-glib1.symbols: - Updated snapd-glib (1.45-0ubuntu0.16.04.1) xenial; urgency=medium * New upstream release (LP: #1793298): - Remove deprecated snapd-login-service - New API: - snapd_app_get_common_id - snapd_client_get_apps2_sync - snapd_client_get_apps2_async - snapd_client_get_apps2_finish - snapd_client_get_maintenance - snapd_client_get_snap_async - snapd_client_get_snap_finish - snapd_client_get_snap_sync - snapd_client_get_snaps_async - snapd_client_get_snaps_finish - snapd_client_get_snap_sync - snapd_maintenance_get_kind - snapd_maintenance_get_message - snapd_media_get_media_type - snapd_media_get_url - snapd_media_get_width - snapd_media_get_height - snapd_snap_get_base - snapd_snap_get_common_ids - snapd_snap_get_media - snapd_snap_get_mounted_from - snapd_snap_get_publisher_display_name - snapd_snap_get_publisher_id - snapd_snap_get_publisher_username - snapd_snap_get_publisher_validation - snapd_system_information_get_build_id - snapd_system_information_get_refresh_hold - snapd_system_information_get_refresh_last - snapd_system_information_get_refresh_next - snapd_system_information_get_refresh_schedule - snapd_system_information_get_refresh_timer - snapd_system_information_get_sandbox_features - SNAPD_ERROR_AUTH_CANCELLED - SNAPD_ERROR_NOT_FOUND - SNAPD_ERROR_NOT_IN_STORE - SNAPD_ERROR_NOT_CLASSIC - SNAPD_ERROR_REVISION_NOT_AVAILABLE - SNAPD_ERROR_CHANNEL_NOT_AVAILABLE - SNAPD_ERROR_NOT_A_SNAP - SNAPD_FIND_FLAGS_SCOPE_WIDE - Deprecated API: - snapd_client_get_apps_sync - snapd_client_get_apps_async - snapd_client_get_apps_finish - snapd_client_list_async - snapd_client_list_finish - snapd_client_list_sync - snapd_login_async - snapd_login_finish - snapd_login_sync - snapd_snap_get_screenshots - Fix buffer overflows reading HTTP chunked data - Reconnect to snapd if disconnected while trying to send the request - Handle short writes to snapd - Remove cancelled requests from the request queue. - Fix SnapdClient reference leak in each request - Fix snapd_snap_match_channel not matching risks correctly - Fix progress callback scope annotations - Fix double-unref on cancelled requests - Support new snap media and mounted-from fields - Support filtering when querying apps - Support snapd maintenance information - Support new error codes - GIR annotation fixes * debian/libsnapd-glib1.symbols: - Updated * debian/control: * debian/snapd-login-service.install - snapd-login-service removed -- Robert Ancell Wed, 06 Mar 2019 15:54:33 +1300 ** Changed in: snapd-glib (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/1793298 Title: snapd-glib changes needed for pulseaudio snap policy module xenial backport Status in snapd-glib source package in Xenial: Fix Released Bug description: [Impact] Older versions of Ubuntu are running older versions of snapd-glib. There have since been bug fixes and support for newer API that was added to snapd since release. [Test Case] 1. Delete existing Snap credentials by deleting keys com.ubuntu.UbuntuOne.GnomeSoftware in Seahorse. 2. Start GNOME Software 3. Install a snap (e.g. moon-buggy) Expected result: User is prompted for Ubuntu credentials and is able to install snap. Observed result: Works as expected (i.e. only looking for regressions). [Regression Potential] There is a risk of breaking existing use cases. This is reduced by the regression tests in the package and the newer versions of snapd-glib working in newer releases. The xenial backport of the fix for 1781428 malfunctioned due to the use of snapd-glib behaviour introduced after the version included in xenial: namely auto-connection (and reconnection) to the snapd socket that was introduced in snapd-glib 1.24. With the policy module loaded, Pulse Audio will contact snapd to check the interfaces plugged by a client in order to decide whether to provide access to the microphone. As the Pulse Audio daemon is long lived, it is not uncommon for the socket connection to be disconnected (either due
[Group.of.nepali.translators] [Bug 1818766] Re: Update to 1.47
This bug was fixed in the package snapd-glib - 1.47-0ubuntu0.16.04.0 --- snapd-glib (1.47-0ubuntu0.16.04.0) xenial; urgency=medium * New upstream release (LP: #1818766) * debian/rules: - Build with --enable-installed-tests * debian/tests/control: * debian/tests/unit: * debian/snapd-glib-tests.install: - Add autopkg tests * debian/libsnapd-glib1.symbols: - Updated snapd-glib (1.45-0ubuntu0.16.04.1) xenial; urgency=medium * New upstream release (LP: #1793298): - Remove deprecated snapd-login-service - New API: - snapd_app_get_common_id - snapd_client_get_apps2_sync - snapd_client_get_apps2_async - snapd_client_get_apps2_finish - snapd_client_get_maintenance - snapd_client_get_snap_async - snapd_client_get_snap_finish - snapd_client_get_snap_sync - snapd_client_get_snaps_async - snapd_client_get_snaps_finish - snapd_client_get_snap_sync - snapd_maintenance_get_kind - snapd_maintenance_get_message - snapd_media_get_media_type - snapd_media_get_url - snapd_media_get_width - snapd_media_get_height - snapd_snap_get_base - snapd_snap_get_common_ids - snapd_snap_get_media - snapd_snap_get_mounted_from - snapd_snap_get_publisher_display_name - snapd_snap_get_publisher_id - snapd_snap_get_publisher_username - snapd_snap_get_publisher_validation - snapd_system_information_get_build_id - snapd_system_information_get_refresh_hold - snapd_system_information_get_refresh_last - snapd_system_information_get_refresh_next - snapd_system_information_get_refresh_schedule - snapd_system_information_get_refresh_timer - snapd_system_information_get_sandbox_features - SNAPD_ERROR_AUTH_CANCELLED - SNAPD_ERROR_NOT_FOUND - SNAPD_ERROR_NOT_IN_STORE - SNAPD_ERROR_NOT_CLASSIC - SNAPD_ERROR_REVISION_NOT_AVAILABLE - SNAPD_ERROR_CHANNEL_NOT_AVAILABLE - SNAPD_ERROR_NOT_A_SNAP - SNAPD_FIND_FLAGS_SCOPE_WIDE - Deprecated API: - snapd_client_get_apps_sync - snapd_client_get_apps_async - snapd_client_get_apps_finish - snapd_client_list_async - snapd_client_list_finish - snapd_client_list_sync - snapd_login_async - snapd_login_finish - snapd_login_sync - snapd_snap_get_screenshots - Fix buffer overflows reading HTTP chunked data - Reconnect to snapd if disconnected while trying to send the request - Handle short writes to snapd - Remove cancelled requests from the request queue. - Fix SnapdClient reference leak in each request - Fix snapd_snap_match_channel not matching risks correctly - Fix progress callback scope annotations - Fix double-unref on cancelled requests - Support new snap media and mounted-from fields - Support filtering when querying apps - Support snapd maintenance information - Support new error codes - GIR annotation fixes * debian/libsnapd-glib1.symbols: - Updated * debian/control: * debian/snapd-login-service.install - snapd-login-service removed -- Robert Ancell Wed, 06 Mar 2019 15:54:33 +1300 ** Changed in: snapd-glib (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/1818766 Title: Update to 1.47 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Xenial: Fix Released Status in snapd-glib source package in Bionic: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Status in snapd-glib source package in Disco: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+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 1823776] Re: /etc/update-motd.d/51-cloudguest is wrong
Fixed in livecd-rootfs 2.525.20 for bionic. ** Changed in: livecd-rootfs (Ubuntu Bionic) 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/1823776 Title: /etc/update-motd.d/51-cloudguest is wrong Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Trusty: New Status in livecd-rootfs source package in Xenial: New Status in livecd-rootfs source package in Bionic: Fix Released Bug description: [SRU Justification] livecd-rootfs creates an /etc/update-motd.d/51-cloudguest in all cloud images that injects wrong information into the motd about Ubuntu Advantage that is not consistent with current product offerings. This file should just be dropped from all cloud images going forward, and we should avoid adding such things in the future in livecd-rootfs sauce. This should be done before the last cloud images are rolled for 14.04 prior to trusty entering ESM. [Regression potential] Nothing should depend on this file's presence in the cloud images. [Test case] Verify that images still build with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1823776/+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 1800610] Re: [SRU] minimize number of manually installed packages
This bug was fixed in the package livecd-rootfs - 2.525.20 --- livecd-rootfs (2.525.20) bionic; urgency=medium [ Steve Langasek ] * Drop /etc/update-motd.d/51-cloudguest from cloud images; this is not consistent with current Ubuntu Advantage product language. Any future customizations to update-motd for cloud images should be done via a package instead. [ Julian Andres Klode ] * Minimize the number of manually installed packages in images by marking dependencies of metapackages as automatically installed. (LP: #1800610); but do not mark direct dependencies of ubiquity as auto installed. This caused cryptsetup to remain auto on the installed system in bionic (see LP #1801629) -- Steve Langasek Thu, 14 Mar 2019 11:04:49 -0700 ** Changed in: livecd-rootfs (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/1800610 Title: [SRU] minimize number of manually installed packages Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in livecd-rootfs source package in Bionic: Fix Released Bug description: [Impact] Releases prior to cosmic mark almost all packages manually installed, meaning that obsolete packages are not autoremoved when they should. We fixed this in cosmic, in trunk r1695, by including a new script that marks as automatically installed all dependencies of manually-installed metapackages. [Test case] Run a build and check in the log that some packages are visited by the script in more than one iterations. [Regression potential] First of all, this does not change existing installations; only new ones. The change can cause packages to be autoremoved that were not autoremoved before after performing a package management operation, or dependency change in packages. The change is essentially safe: Since we only mark dependencies of packages in the section "metapackages", and since those receive special treatment by apt: 1. removal due to dependencies/conflicts: the manual bit transfers from the meta to its deps 2. explicit removal (apt remove meta): meta and its dependencies are removed It is not possible to accidentally uninstall the entire metapackage with its dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1800610/+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 1816642] Re: SRU of LXC 2.0.11
Adding go-lxc to this as the fixes in 2.0.11 ended up showing bugs in go-lxc's test logic, so we'll have to cherry-pick a couple of fixes from upstream to have it be happy and give us a meaningful test result. ** Also affects: golang-gopkg-lxc-go-lxc.v2 (Ubuntu) Importance: Undecided Status: New ** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu) Status: New => Fix Released ** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Trusty) Status: New => Triaged ** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial) Status: New => In Progress ** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Trusty) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1816642 Title: SRU of LXC 2.0.11 Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty: Triaged Status in lxc source package in Trusty: Triaged Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial: In Progress Status in lxc source package in Xenial: Fix Committed Bug description: LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch. This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog for both of them can be found below: LXC 2.0.11: - autotools: handle getgrgid_r on bionic - autotools: add memory_utils.h to Makefile.am - change version to 2.0.11 in configure.ac LXC 2.0.10: - tools: allow lxc-attach to undefined containers - utils: move memfd_create() definition - utils: add lxc_cloexec() - utils: add lxc_make_tmpfile() - utils: add lxc_getpagesize() - utils: add lxc_safe_long_long() - utils: parse_byte_size_string() - utils: add lxc_find_next_power2() - namespace: use lxc_getpagesize() - lxc-debian: allow creating `testing` and `unstable` - Call lxc_config_define_load from lxc_execute again - Fix typo in lxc-net script - Add missing lxc_container_put - lxc-debian: don't write C.* locales to /etc/locale.gen - attach: correctly handle namespace inheritance - cgfsng: fix cgroup2 detection - cgroups: enable container without CAP_SYS_ADMIN - lxc-start: remove unnecessary checks - start: close non-needed file descriptors - handler: make name argument const - start: close data socket in parent - monitor: do not log useless warnings - network: reap child in all cases - conf: reap child in all cases - storage: switch to ext4 as default filesystem - tools: fix help output of lxc-create - attach: handle namespace inheritance - cgroups/cgfsng: keep mountpoint intact - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown() - cgroups/cgfsng: support MS_READONLY with cgroup ns - log: check for i/o error with vsnprintf() - cgroupfs/cgfsng: tweak logging - cgroups/cgfsng: remove is_lxcfs() - cgroups/cgfsng: fix get_controllers() for cgroup2 - cgroupfs/cgfsng: improve cgroup2 handling - config: remove SIGRTMIN+14 as lxc.signal.stop - commands: non-functional changes - console: non-functional changes - console: non-functional changes - lxc-test-unpriv: fix the overlayfs mount error - attach: allow attach with empty conf - tools/lxc_attach: removed api logging - console: fix console info message - Add missing dependency libunistring - cgroups/cgfsng: adapt to new cgroup2 delegation - console: report detach message on demand - lxccontainer: enable daemonized app containers - console: use correct escape sequence check - console: prepare for generic signal handler - console: exit mainloop on SIGTERM - commands: non-functional changes - lxccontainer: non-functional changes - commands: fix state socket implementation - lxc_init: set the control terminal in the child session - lxc-test-unpriv: check user existence before removing it - Fixed typo on lxc.spec.in - conf: move CAP_SYS_* definitions to utils.h - start.c: always switch uid and gid - Use AX_PTHREAD config script to detect pthread api - utils.h: Avoid duplicated sethostname implementation - tools/lxc_cgroup: remove internal logging - tools/lxc_autostart: remove internal logging - tools/lxc_clone: remove internal logging - tools/lxc_console: remove internal logging - tools/lxc_create: remove internal logging - tools/lxc_destroy: remove internal logging - tools/lxc_device: remove internal logging - tools/lxc_execute: removed internal logging - tools/lxc_freeze: remove internal logging - tools/lxc_info: removed internal logging - criu: detect veth name -
[Group.of.nepali.translators] [Bug 1822804] Re: linux-aws-hwe: 4.15.0-1036.38~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822805 - phase: Ready for Packaging - phase-changed: Friday, 05. April 2019 14:41 UTC + phase: Packaging + phase-changed: Tuesday, 09. April 2019 13:12 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822804 Title: linux-aws-hwe: 4.15.0-1036.38~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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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-aws-hwe package in Ubuntu: Invalid Status in linux-aws-hwe source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822805 phase: Packaging phase-changed: Tuesday, 09. April 2019 13:12 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822804/+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 1822814] Re: linux-azure-edge: 4.15.0-1042.46 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1822817 - phase: Packaging - phase-changed: Tuesday, 09. April 2019 09:42 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 09. April 2019 13:13 UTC reason: - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Pending -- ready for review -- 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/1822814 Title: linux-azure-edge: 4.15.0-1042.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: 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: 1822817 phase: Ready for Promote to Proposed phase-changed: Tuesday, 09. April 2019 13:13 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822814/+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 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 - phase: Promote to Proposed - phase-changed: Tuesday, 09. April 2019 10:11 UTC + phase: Testing + phase-changed: Tuesday, 09. April 2019 13:13 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- 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/1822811 Title: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1822812 phase: Testing phase-changed: Tuesday, 09. April 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+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 1822814] Re: linux-azure-edge: 4.15.0-1042.46 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822817 - phase: Ready for Packaging - phase-changed: Thursday, 04. April 2019 17:09 UTC + phase: Packaging + phase-changed: Tuesday, 09. April 2019 09:42 UTC reason: - prepare-package-meta: Pending -- version not specified + prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822814 Title: linux-azure-edge: 4.15.0-1042.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge 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: 1822817 phase: Packaging phase-changed: Tuesday, 09. April 2019 09:42 UTC reason: prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822814/+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 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
The referenced patch fixes an earlier commit [1] that was added in the
3.11 time frame so Trusty needs this too.
[1] 74f84a5726c7 ("openvswitch: Copy individual actions.")
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1813244
Title:
systemd cause kernel trace "BUG: unable to handle kernel paging
request at 6db23a14" on Cosmic i386
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Trusty:
Confirmed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
SRU Justification:
[Impact]
* Flow action buffer can be incorrectly resized to contain the newly
added action entries: the buffer is always resized multiplying the
previous size by 2, but this might be not enough if the requested size
is bigger than previous_size*2, causing a buffer overflow
* The fix correctly resizes the buffer to prevent the buffer overflow
* Despite the subject this bug can be triggered potentially on any
architecture, but it is very likely to happen on i386 running the
following test case
[Test Case]
* run this openvswitch test case:
https://launchpadlibrarian.net/416589265/lp1262692
[Fix]
* Instead of resizing the buffer by a factor of 2, use
max(current_size * 2, current_size + requested_size)
[Regression Potential]
* Fix has been tested on the affected platform and verified using
slub_debug. The patch has been queued up for -stable by David Miller,
it will be included upstream for the next merge window. It is also a
very small patch (a one-liner basically), so backport changes are
minimal.
[Original bug report]
This issue was found after leaving a SUT to run overnight (was testing
the ubuntu_cts_kernel test 13 hours ago before this happens). Can't
tell if this is a regression, as I haven't find a way to reproduce it.
But I do see similar reports on the Internet [1]
After checking the systemd service timers, it looks like this is
caused by the logrotate.service:
$ sudo systemctl list-timers --all
NEXT LEFT LAST
PASSEDUNIT ACTIVATES
Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h
ago apt-daily-upgrade.timer apt-daily-upgrade.service
Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min
ago apt-daily.timer apt-daily.service
Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min
ago motd-news.timer motd-news.service
Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h
38min ago logrotate.timer logrotate.service
Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min
ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv
Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day
17h ago fstrim.timer fstrim.service
n/a n/a n/a n/a
snapd.snap-repair.timer snapd.snap-repair.service
7 timers listed.
After this happens, you won't be able to reboot it with the command.
$ sudo reboot
sudo: unable to resolve host onza: Resource temporarily unavailable
Killed
Here is the error message, please refer to the attachment for a
complete syslog:
Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files...
Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel
paging request at 6db23a14
Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde =
Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP
Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm:
systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu
Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc.
PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012
Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240
Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45
f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39
45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f
85 3f 01
Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX:
350d EDX: 350c
Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP:
f461fd9c ESP: f461fd74
Jan 25 00:00:37 onza kernel: [45283.024304]
