[Bug 1851623] Re: Enable framebuffer fonts auto selection for HighDPI screen
Screenshot before applying the patch. ** Description changed: == Justification == After bug 1819881 - [CONFIG] please enable highdpi font FONT_TER16x32, our kernels now support TER16x32 font for high resolution screen. With Takashi's patch: dfd19a50 (fonts: Prefer a bigger font for high resolution screens) The framebuffer can now decide which font to use base on the screen resolution. It will be great to have this feature in older kernels as well. == Fixes == * aa1d19f1 (fonts: Fix coding style) * dfd19a50 (fonts: Prefer a bigger font for high resolution screens) First patch just changes the coding style, no actual changes were made. The second patch added an extra check to see if we can use highDPI font. These two patches can be cherry-picked into X/B/D For Eoan and onward, they already have these patches. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1851623-fb-font-detect/ Patch tested on a Dell UHD laptop and it works as expected, the font displayed in the early boot stage has been set to a more readable one. + Screenshots can be found in the attachment of the bug report. + == Regression Potential == Low, this only affects the frame buffer, changing the way to decide which font to use. ** Attachment added: "WithoutPatch.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+attachment/5303425/+files/WithoutPatch.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851623 Title: Enable framebuffer fonts auto selection for HighDPI screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851623] Re: Enable framebuffer fonts auto selection for HighDPI screen
With patched Bionic kernel. ** Attachment added: "Patched-B.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+attachment/5303427/+files/Patched-B.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851623 Title: Enable framebuffer fonts auto selection for HighDPI screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851507] Re: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker
** 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Thursday, 07. November 2019 09:28 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait replaces: bug 1850799 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851507 Title: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851623] Re: Enable framebuffer fonts auto selection for HighDPI screen
With patched Disco kernel. ** Attachment added: "Patched-D.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+attachment/5303426/+files/Patched-D.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851623 Title: Enable framebuffer fonts auto selection for HighDPI screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851623] Re: Enable framebuffer fonts auto selection for HighDPI screen
With patched Xenial kernel. ** Attachment added: "Patched-X.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+attachment/5303428/+files/Patched-X.jpg ** Description changed: == Justification == After bug 1819881 - [CONFIG] please enable highdpi font FONT_TER16x32, our kernels now support TER16x32 font for high resolution screen. With Takashi's patch: dfd19a50 (fonts: Prefer a bigger font for high resolution screens) The framebuffer can now decide which font to use base on the screen resolution. It will be great to have this feature in older kernels as well. == Fixes == * aa1d19f1 (fonts: Fix coding style) * dfd19a50 (fonts: Prefer a bigger font for high resolution screens) First patch just changes the coding style, no actual changes were made. The second patch added an extra check to see if we can use highDPI font. These two patches can be cherry-picked into X/B/D For Eoan and onward, they already have these patches. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1851623-fb-font-detect/ - Patch tested on a Dell UHD laptop and it works as expected, the font - displayed in the early boot stage has been set to a more readable one. + Patch tested on a Dell G7 UHD laptop and it works as expected, the font + displayed in the early boot stage (before switching to color frame + buffer device) has been set to a more readable one. Screenshots can be found in the attachment of the bug report. == Regression Potential == Low, this only affects the frame buffer, changing the way to decide which font to use. ** Description changed: == Justification == After bug 1819881 - [CONFIG] please enable highdpi font FONT_TER16x32, our kernels now support TER16x32 font for high resolution screen. With Takashi's patch: dfd19a50 (fonts: Prefer a bigger font for high resolution screens) The framebuffer can now decide which font to use base on the screen resolution. It will be great to have this feature in older kernels as well. == Fixes == * aa1d19f1 (fonts: Fix coding style) * dfd19a50 (fonts: Prefer a bigger font for high resolution screens) First patch just changes the coding style, no actual changes were made. The second patch added an extra check to see if we can use highDPI font. These two patches can be cherry-picked into X/B/D For Eoan and onward, they already have these patches. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1851623-fb-font-detect/ Patch tested on a Dell G7 UHD laptop and it works as expected, the font displayed in the early boot stage (before switching to color frame - buffer device) has been set to a more readable one. + buffer device) will be set to a more readable one. Screenshots can be found in the attachment of the bug report. == Regression Potential == Low, this only affects the frame buffer, changing the way to decide which font to use. ** Description changed: == Justification == After bug 1819881 - [CONFIG] please enable highdpi font FONT_TER16x32, our kernels now support TER16x32 font for high resolution screen. - With Takashi's patch: + With Takashi Iwai's patch: dfd19a50 (fonts: Prefer a bigger font for high resolution screens) The framebuffer can now decide which font to use base on the screen resolution. It will be great to have this feature in older kernels as well. == Fixes == * aa1d19f1 (fonts: Fix coding style) * dfd19a50 (fonts: Prefer a bigger font for high resolution screens) First patch just changes the coding style, no actual changes were made. The second patch added an extra check to see if we can use highDPI font. These two patches can be cherry-picked into X/B/D For Eoan and onward, they already have these patches. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1851623-fb-font-detect/ Patch tested on a Dell G7 UHD laptop and it works as expected, the font displayed in the early boot stage (before switching to color frame buffer device) will be set to a more readable one. Screenshots can be found in the attachment of the bug report. == Regression Potential == Low, this only affects the frame buffer, changing the way to decide which font to use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851623 Title: Enable framebuffer fonts auto selection for HighDPI screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850827] Re: nvidia-graphics-drivers-430 430.50-0ubuntu3 ADT test failure with linux 5.4.0-3.4
This is fixed in focal-proposed: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/440.31-0ubuntu1 The 440 series replaces the 430 series, and it builds correctly with Linux 5.4 :~# dkms status nvidia, 440.31, 5.3.0-21-generic, x86_64: installed nvidia, 440.31, 5.4.0-4-generic, x86_64: installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850827 Title: nvidia-graphics-drivers-430 430.50-0ubuntu3 ADT test failure with linux 5.4.0-3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1850827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821364] Re: xfce4 install on Ubuntu 18.04 has no polkit agent
** Changed in: xfce4 (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821364 Title: xfce4 install on Ubuntu 18.04 has no polkit agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1821364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681839] Re: libvirt: blockcommit fails - disk not ready for pivot yet
FYI: my pre-checks on the PPA build 1.3.1-1ubuntu10.29~ppa1 look good. prep (x86_64): Pass 25 F/S/N 0/0/0 - RC 0 (17 min 84141 lin) migrate (x86_64) : Pass 232 F/S/N 0/12/0 - RC 0 (63 min 104302 lin) cross (x86_64) : Pass 64 F/S/N 0/1/0 - RC 0 (70 min 94458 lin) misc (x86_64): Pass 76 F/S/N 0/0/0 - RC 0 (18 min 29606 lin) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681839 Title: libvirt: blockcommit fails - disk not ready for pivot yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1681839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673357] Re: Munin core plugin "if_" doesn't work
** Changed in: munin (Ubuntu Xenial) Status: New => Triaged ** Changed in: munin (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673357 Title: Munin core plugin "if_" doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1673357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673357] Re: Munin core plugin "if_" doesn't work
** Changed in: munin (Ubuntu Xenial) Status: New => Triaged ** Changed in: munin (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1673357 Title: Munin core plugin "if_" doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1673357/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1851234] Re: [SRU] libreoffice 6.3.3 for eoan
** Changed in: libreoffice (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851234 Title: [SRU] libreoffice 6.3.3 for eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1851234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851655] [NEW] sync_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3 i386
Public bug reported: sync_file_range02 from ubuntu_ltp_syscalls failed on i386 node pepe with B-hwe-edge 5.3 kernel Test failed with: sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25317376, expected 16777216 startup='Thu Nov 7 09:15:20 2019' sync_file_range01 1 TPASS : got expected error: TEST_ERRNO=EBADF(9): Bad file descriptor sync_file_range01 2 TPASS : got expected error: TEST_ERRNO=ESPIPE(29): Illegal seek sync_file_range01 3 TPASS : got expected error: TEST_ERRNO=EINVAL(22): Invalid argument sync_file_range01 4 TPASS : got expected error: TEST_ERRNO=EINVAL(22): Invalid argument sync_file_range01 5 TPASS : got expected error: TEST_ERRNO=EINVAL(22): Invalid argument tag=sync_file_range01 stime=1573118120 dur=1 exit=exited stat=0 core=no cu=0 cs=0 startup='Thu Nov 7 09:15:22 2019' tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop0' tst_supported_fs_types.c:59: INFO: Kernel supports ext2 tst_supported_fs_types.c:43: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:59: INFO: Kernel supports ext3 tst_supported_fs_types.c:43: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:59: INFO: Kernel supports ext4 tst_supported_fs_types.c:43: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:59: INFO: Kernel supports xfs tst_supported_fs_types.c:43: INFO: mkfs.xfs does exist tst_supported_fs_types.c:59: INFO: Kernel supports btrfs tst_supported_fs_types.c:43: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:59: INFO: Kernel supports vfat tst_supported_fs_types.c:43: INFO: mkfs.vfat does exist tst_supported_fs_types.c:82: INFO: Filesystem exfat is not supported tst_test.c:1278: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25317376, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25303040, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts='' mke2fs 1.44.1 (24-Mar-2018) tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25171968, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25165824, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop0 with btrfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 27258880, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write tst_test.c:1278: INFO: Testing on vfat tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:111: INFO: Pre-filling file sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 25192448, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write Summary: passed 12 failed 6 skipped 0 warnings 0 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 5.3 bionic i386 sru-20191021 ubuntu-ltp-syscalls ** Tags added: i386 sru-20191021 ubuntu-ltp-syscalls ** Tags added: 5.3 bionic ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851655 Title: sync_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3 i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849608] Re: systemd resolv should separate the output of stdout and stderr
Hello Steven, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Eoan) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849608 Title: systemd resolv should separate the output of stdout and stderr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831787] Re: Bogus routes after DHCP lease change
Hello Ante, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831787 Title: Bogus routes after DHCP lease change To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1831787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
Hello Paul, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
Hello Dan, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1835581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837734] Re: libnss3 reads fips_enabled flag and automatically switches to FIPS mode
** Merge proposal unlinked: https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1837734 Title: libnss3 reads fips_enabled flag and automatically switches to FIPS mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1837734/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744328] Re: libfreebl3.so should be public, not in the nss subdir
** Merge proposal unlinked: https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1744328 Title: libfreebl3.so should be public, not in the nss subdir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850653] Re: realmode in ubuntu_kvm_unit tests fails/ E-Azure
Spotted on Eoan bare-metal amd64 node gonzo 71. 11/01 14:00:18 DEBUG| utils:0153| [stdout] FAIL: iret 1 72. 11/01 14:00:18 DEBUG| utils:0153| [stdout] PASS: iret 2 73. 11/01 14:00:18 DEBUG| utils:0153| [stdout] FAIL: iret 3 ** Tags added: ubuntu-kvm-unit-tests ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850653 Title: realmode in ubuntu_kvm_unit tests fails/ E-Azure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1850653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851520] Re: Online Accounts Cannot Add Gmail Account
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webkit2gtk (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851520 Title: Online Accounts Cannot Add Gmail Account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1851520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813018] Re: Kernel Oops - unable to handle kernel paging request; RIP is at wait_migrate_huge_page+0x51/0x70
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813018 Title: Kernel Oops - unable to handle kernel paging request; RIP is at wait_migrate_huge_page+0x51/0x70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837734] Re: libnss3 reads fips_enabled flag and automatically switches to FIPS mode
** Merge proposal unlinked: https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837734 Title: libnss3 reads fips_enabled flag and automatically switches to FIPS mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1837734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849343] Re: core18 builds failing on bionic due to bash typo
Just ran a bionic based ubuntu-core image build via cdimage (with proposed enabled) and the builds succeeded: https://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-core/bionic/daily-live-20191107.log Confirmed the typo is no longer hindering the image builds. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849343 Title: core18 builds failing on bionic due to bash typo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1849343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580385] Re: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures
** Patch added: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+attachment/5303499/+files/bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580385 Title: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580385] Re: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures
** Patch added: "xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+attachment/5303500/+files/xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580385 Title: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850754] Re: ceph-volume lvm list is O(n^2)
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850754 Title: ceph-volume lvm list is O(n^2) To manage notifications about this bug go to: https://bugs.launchpad.net/ceph/+bug/1850754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
> it will prevent udevd from running the rules against it. Thus effectively the event will be fired and done, but nothing actually executed for it. Interesting, I suspect this is the race we see. The events emitted but no actions taken (ie we didn't get our by-partuuid symlink created. > I somehow wonder if we even need partx call, if we properly flock the device and trigger udev after everything is done. Growpart is modifying the partition table of the root device which is already mounted. We will not be able to flock the root device since it's open and mounted. This is precisely why we need to use the partx call as it updates the kernel partition table mapping without requiring an exclusive lock on the device. > So does growpart create partition? move it? delete/recreate one? i.e does ADD happen? or like REMOVE & ADD? or maybe it's like just MOVE or CHANGE? Do we have logs of the emitted events already? growpart on gpt, uses sgdisk which, deletes and then recreates the existing partition but with a larger size. The logs are above, see comment #22 -> #24 and #38. > Don't like flags, as then we'll have to supported forever =) maybe env variable? or like simply change in focal and compare focal vs eoan? This may not matter if we can't flock. I suspect we'll need to use the ugly re-trigger events for the disk. growpart could take the disk it's pointed at, examine the existing udevadm symlinks associated with this (via udevadm info --export), perform it's operation, and then post- operation, trigger the add event on the disk, settle, and confirm that udevadm info --export contains the same set of links (partuuid ,etc). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851666] [NEW] In Ubuntu 19.10 when I runs dosbox 0.74, left hand side items of unity favourites are visible with a faded shadow.
Public bug reported: When I runs dosbox 0.74 in fullscreen mode, unity items are visible in a disabled mode and screen becomes confusing too. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 7 20:52:48 2019 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2017-11-08 (729 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-11-06 (0 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851666 Title: In Ubuntu 19.10 when I runs dosbox 0.74, left hand side items of unity favourites are visible with a faded shadow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1851666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851507] Re: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker
** 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 07. November 2019 14:02 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851507 Title: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Stalled -- packages are in the wrong component + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851679] [NEW] power manager crashes at each logon
Public bug reported: xfce4-power-manager crash each and every time at logon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xfce4-power-manager 1.6.5-2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Nov 7 11:17:26 2019 InstallationDate: Installed on 2019-10-12 (26 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to eoan on 2019-11-04 (2 days ago) ** Affects: xfce4-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851679 Title: power manager crashes at each logon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1851679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850994] Re: ubuntu-aufs-modified mmap_region() breaks refcounting in overlayfs/shiftfs error path
Patches sent: https://lists.ubuntu.com/archives/kernel- team/2019-November/105302.html Opened bug 1851677 for overlapping s_iflags. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850994 Title: ubuntu-aufs-modified mmap_region() breaks refcounting in overlayfs/shiftfs error path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849491] Re: Add support for EXTRA_SNAPS in bionic
This bug was fixed in the package livecd-rootfs - 2.525.33 --- livecd-rootfs (2.525.33) bionic; urgency=medium * Add support for the 'kassel' subflavor of UC18 images. (LP: #1850674) livecd-rootfs (2.525.32) bionic; urgency=medium * Fix a terrible typo in auto/build that causes all core18 builds to fail on this series (LP: #1849343). * Backport 999-ubuntu-image-customization.chroot to have a common place for our cloud-init datasource. Add some modifications on top to make sure the legacy raspi2 configuration stays the same (LP: #1849472). * Backport enabling of adding extra snaps to ubuntu-core images via the EXTRA_SNAPS environment (LP: #1849491). -- Łukasz 'sil2100' Zemczak Wed, 30 Oct 2019 18:09:02 +0100 ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849491 Title: Add support for EXTRA_SNAPS in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1849491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850674] Update Released
The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850674 Title: Support amd64+kassel in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1850674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849491] Re: Add support for EXTRA_SNAPS in bionic
This bug was fixed in the package livecd-rootfs - 2.408.56 --- livecd-rootfs (2.408.56) xenial; urgency=medium * Backport enabling of adding extra snaps to ubuntu-core images via the EXTRA_SNAPS environment (LP: #1849491). -- Łukasz 'sil2100' Zemczak Wed, 30 Oct 2019 17:28:57 +0100 ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849491 Title: Add support for EXTRA_SNAPS in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1849491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851677] [NEW] s_iflags overlap prevents unprivileged overlayfs mounts
Public bug reported: As reported by Jann Horn on bug 1850994, unprivileged overlayfs mounting fails in disco/eoan due to SB_I_NOSUID and SB_I_USERNS_VISIBLE. overlayfs sets SB_I_NOSUID for unprivileged mounts, which causes mount_too_revealing() to bail out as it sees SB_I_USERNS_VISIBLE as being set. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851677 Title: s_iflags overlap prevents unprivileged overlayfs mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849483] Re: shiftfs: prevent exceeding project quotas
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849483 Title: shiftfs: prevent exceeding project quotas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851677] Re: s_iflags overlap prevents unprivileged overlayfs mounts
** Description changed: As reported by Jann Horn on bug 1850994, unprivileged overlayfs mounting fails in disco/eoan due to SB_I_NOSUID and SB_I_USERNS_VISIBLE. overlayfs sets SB_I_NOSUID for unprivileged mounts, which causes mount_too_revealing() to bail out as it sees SB_I_USERNS_VISIBLE as being set. - - Xenial has a differing conflict of s_iflags, which does not prevent - unprivileged overlayfs mounts, but it should still be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851677 Title: s_iflags overlap prevents unprivileged overlayfs mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847036] Re: changeme.py crashed with SIGSEGV
Hello James, or anyone else affected, Accepted python3.7 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.7/3.7.5-2~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python3.7 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847036 Title: changeme.py crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.7/+bug/1847036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5
Hello Matthias, or anyone else affected, Accepted python3.7 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.7/3.7.5-2~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python3.7 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: python3.6 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Stalled -- copy FAILED + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840835] Re: High power consumption using 5.0.0-25-generic
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840835 Title: High power consumption using 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851677] Re: s_iflags overlap prevents unprivileged overlayfs mounts
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851677 Title: s_iflags overlap prevents unprivileged overlayfs mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833618] Re: MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB pendrive in this case).
BIONIC VERIFICATION: Nov 07 13:30:27 kbionic kernel: usb-storage 1-6:1.0: USB Mass Storage device detected Nov 07 13:30:27 kbionic kernel: scsi host2: usb-storage 1-6:1.0 Nov 07 13:30:27 kbionic kernel: usbcore: registered new interface driver usb-storage Nov 07 13:30:27 kbionic kernel: usbcore: registered new interface driver uas Nov 07 13:30:27 kbionic mtp-probe[196132]: checking bus 1, device 5: "/sys/devices/pci:00/:00:14.0/usb1/1-6" Nov 07 13:30:27 kbionic mtp-probe[196132]: bus: 1, device: 5 was not an MTP device Nov 07 13:30:28 kbionic kernel: scsi 2:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4 Nov 07 13:30:28 kbionic kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0 Nov 07 13:30:28 kbionic kernel: sd 2:0:0:0: [sdb] 15728640 512-byte logical blocks: (8.05 GB/7.50 GiB) Nov 07 13:30:28 kbionic kernel: sd 2:0:0:0: [sdb] Write Protect is off Nov 07 13:30:28 kbionic kernel: sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00 Nov 07 13:30:28 kbionic kernel: sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Nov 07 13:30:28 kbionic kernel: sdb: sdb1 Nov 07 13:30:28 kbionic kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk Nov 07 13:30:28 kbionic systemd-udevd[196128]: Process '/usr/bin/sg_inq --export --inhex=/sys/block/sdb/device/vpd_pg80 --raw' failed with exit code 15. Nov 07 13:30:28 kbionic systemd-udevd[196128]: Process '/usr/bin/sg_inq --export --inhex=/sys/block/sdb/device/vpd_pg83 --raw' failed with exit code 15. Nov 07 13:31:22 kbionic PackageKit[186101]: daemon quit Nov 07 13:31:22 kbionic systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM Nov 07 13:31:22 kbionic systemd[1]: packagekit.service: Succeeded. P: /devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/host2/target2:0:0/2:0:0:0/block/sdb N: sdb L: 0 S: disk/by-id/usb-Generic_Flash_Disk_A3E8C929-0:0 S: disk/by-path/pci-:00:14.0-usb-0:6:1.0-scsi-0:0:0:0 E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/host2/target2:0:0/2:0:0:0/block/sdb E: SUBSYSTEM=block E: DEVNAME=/dev/sdb E: DEVTYPE=disk E: MAJOR=8 E: MINOR=16 E: USEC_INITIALIZED=101644953827 E: SCSI_TPGS=0 E: SCSI_TYPE=disk E: SCSI_VENDOR=Generic E: SCSI_VENDOR_ENC=Generic\x20 E: SCSI_MODEL=Flash_Disk E: SCSI_MODEL_ENC=Flash\x20Disk\x20\x20\x20\x20\x20\x20 E: SCSI_REVISION=8.07 E: ID_SCSI=1 E: ID_SCSI_SN=1 E: ID_SCSI_DI=1 E: ID_VENDOR=Generic E: ID_VENDOR_ENC=Generic\x20 E: ID_MODEL=Flash_Disk E: ID_MODEL_ENC=Flash\x20Disk\x20\x20\x20\x20\x20\x20 E: ID_REVISION=8.07 E: ID_TYPE=disk E: ID_VENDOR_ID=058f E: ID_MODEL_ID=6387 E: ID_SERIAL=Generic_Flash_Disk_A3E8C929-0:0 E: ID_SERIAL_SHORT=A3E8C929 E: ID_INSTANCE=0:0 E: ID_BUS=usb E: ID_USB_INTERFACES=:080650: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_DRIVER=usb-storage E: ID_PATH=pci-:00:14.0-usb-0:6:1.0-scsi-0:0:0:0 E: ID_PATH_TAG=pci-_00_14_0-usb-0_6_1_0-scsi-0_0_0_0 E: ID_PART_TABLE_UUID=01b60b77 E: ID_PART_TABLE_TYPE=dos E: net.ifnames=0 E: DEVLINKS=/dev/disk/by-id/usb-Generic_Flash_Disk_A3E8C929-0:0 /dev/disk/by-path/pci-:00:14.0-usb-0:6:1.0-scsi-0:0:0:0 E: TAGS=:systemd: USB serial is good and sg_inqXX failed as expected. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833618 Title: MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB pendrive in this case). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sg3-utils/+bug/1833618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657646] Re: [20.04] Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation
** Changed in: ubuntu-power-systems Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: [20.04] Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1657646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Promote to Proposed phase-changed: Wednesday, 06. November 2019 20:58 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + promote-to-proposed: Stalled -- copy FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /
** Tags removed: server-triage-discuss ubuntu-server -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1582899 Title: in-target: mkinitramfs: failed to determine device for / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /
** Tags removed: server-triage-discuss ubuntu-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582899 Title: in-target: mkinitramfs: failed to determine device for / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413665] Re: Bad Request - Bad bot, go away! Request aborted.
It seems any password auto filler gets fooled by the honeypot on the page and results in the error. The irony is that in order to comment or mark "it affects me", you have to get past the very form that's causing the problem. I suspect this affects a lot more people than is indicated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413665 Title: Bad Request - Bad bot, go away! Request aborted. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1413665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849491] Re: Add support for EXTRA_SNAPS in bionic
The same seems to work for xenial as well, the test livefs build seems to include the requested extra snap: https://launchpadlibrarian.net/450309814 /buildlog_ubuntu_xenial_amd64_ubuntu-core_BUILDING.txt.gz ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849491 Title: Add support for EXTRA_SNAPS in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1849491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850994] Re: ubuntu-aufs-modified mmap_region() breaks refcounting in overlayfs/shiftfs error path
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850994 Title: ubuntu-aufs-modified mmap_region() breaks refcounting in overlayfs/shiftfs error path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849563] Re: Unable to passthrough GPUs to guest
** Changed in: edk2 (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849563 Title: Unable to passthrough GPUs to guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1849563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848211] Re: valgrind fails to use debug symbols from glib/gtk
This seems similar to LP: #1843479 , maybe strip is broken, will check. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211 Title: valgrind fails to use debug symbols from glib/gtk To manage notifications about this bug go to: https://bugs.launchpad.net/valgrind/+bug/1848211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811496] Re: Make grub-ipxe work under UEFI
Yeah it's ready for upload but no Debian or Ubuntu developer seems to have time to upload it. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811496 Title: Make grub-ipxe work under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1811496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835738] Please test proposed package
Hello Matthias, or anyone else affected, Accepted python3.6 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.6/3.6.9-1~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847036] Re: changeme.py crashed with SIGSEGV
Please ignore the SRU bug comment above - this SRU is handled via a single SRU tracking bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847036 Title: changeme.py crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.7/+bug/1847036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -proposed tracker
** 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850486 Title: eoan/linux: 5.3.0-21.22 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
I have a very similar issue with another Samsung laptop: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851684] [NEW] python3.8-venv should depend on python3-distutils
Public bug reported: Originally reported here: https://github.com/deadsnakes/issues/issues/97 I'm also surprised to see a package added to LTS so late in the game, is there a change in policy around new packages / feature bumps that I missed? Here's a reproduction using docker: ``` FROM ubuntu:bionic RUN apt-get update && apt-get install -yq python3.8-venv RUN python3.8 -m venv /venv ``` ``` Step 3/3 : RUN python3.8 -m venv /venv ---> Running in 41a792e03c49 The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command. apt-get install python3-venv You may need to use sudo with that command. After installing the python3-venv package, recreate your virtual environment. Failing command: ['/venv/bin/python3.8', '-Im', 'ensurepip', '-- upgrade', '--default-pip'] The command '/bin/sh -c python3.8 -m venv /venv' returned a non-zero code: 1 ``` The inner (hidden) error: ``` root@f806220c24ec:/# python3.8 -mvenv /venv The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package using the following command. apt-get install python3-venv You may need to use sudo with that command. After installing the python3-venv package, recreate your virtual environment. Failing command: ['/venv/bin/python3.8', '-Im', 'ensurepip', '-- upgrade', '--default-pip'] root@f806220c24ec:/# /venv/bin/python -m ensurepip Traceback (most recent call last): File "/usr/lib/python3.8/ensurepip/__init__.py", line 54, in _run_pip import pip._internal File "", line 259, in load_module File "/tmp/tmpmmf52da_/pip-9.0.1-py2.py3-none-any.whl/pip/__init__.py", line 29, in File "", line 259, in load_module File "/tmp/tmpmmf52da_/pip-9.0.1-py2.py3-none-any.whl/pip/utils/__init__.py", line 23, in File "", line 259, in load_module File "/tmp/tmpmmf52da_/pip-9.0.1-py2.py3-none-any.whl/pip/locations.py", line 9, in ImportError: cannot import name 'sysconfig' from 'distutils' (/usr/lib/python3.8/distutils/__init__.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.8/runpy.py", line 192, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib/python3.8/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3.8/ensurepip/__main__.py", line 5, in sys.exit(ensurepip._main()) File "/usr/lib/python3.8/ensurepip/__init__.py", line 263, in _main return _bootstrap( File "/usr/lib/python3.8/ensurepip/__init__.py", line 181, in _bootstrap return _run_pip(args + _PROJECTS, additional_paths) File "/usr/lib/python3.8/ensurepip/__init__.py", line 57, in _run_pip import pip File "", line 259, in load_module File "/venv/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/__init__.py", line 29, in File "", line 259, in load_module File "/venv/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/utils/__init__.py", line 23, in File "", line 259, in load_module File "/venv/share/python-wheels/pip-9.0.1-py2.py3-none-any.whl/pip/locations.py", line 9, in ImportError: cannot import name 'sysconfig' from 'distutils' (/usr/lib/python3.8/distutils/__init__.py) ``` ** Affects: python3.8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851684 Title: python3.8-venv should depend on python3-distutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1851684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850485] Re: bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1850486 packages: main: linux-hwe-edge meta: linux-meta-hwe-edge signed: linux-signed-hwe-edge - phase: Testing - phase-changed: Wednesday, 30. October 2019 22:56 UTC + phase: Holding before Promote to Updates + phase-changed: Thursday, 07. November 2019 17:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850485 Title: bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850117] Re: [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE kernel branch
Just a clarification, the description says "hpre patchset have merged into mainline 5.4rc3 kernel", however it has not: $ git log --pretty=oneline --abbrev-commit v5.3..v5.4-rc6 --grep "crypto: hisilicon - add HiSilicon HPRE accelerator" But it is in linux-next: $ git log --pretty=oneline --abbrev-commit v5.3..linux-next/master --grep "crypto: hisilicon - add HiSilicon HPRE accelerator" 5b243b6c4aa21 crypto: hisilicon: Fix misuse of GENMASK macro c8b4b477079d1 crypto: hisilicon - add HiSilicon HPRE accelera -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850117 Title: [hpre-1017]sync mainline kernel 5.4rc3 hpre patchset into ubuntu HWE kernel branch To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1850117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851675] [NEW] dpkg fails to properly invoke ldconfig
Public bug reported:
Seen on: Ubuntu 18.04.3 LTS
dpkg version: 1.19.0.5ubuntu2.3 (also in 1.19.0.5ubuntu2.2)
Regression compared to dpkg 1.19.0.5ubuntu2.1
To reproduce this:
1. You need a package that depends on a library for running a script in its
postinst hook. For instance, the attached minimal package has `Depends:
python-augeas`, and tries to do “from augeas import Augeas” in a script invoked
from the postinst hook. (It does nothing else.)
2. Make sure the dependent library is not yet installed. In this example:
libaugeas0, which is a dependency of python-augeas.
3. apt-get install the package. For the attached exmple, you can use `dpkg -i`,
followed by `apt-get -f install`.
Result:
Setting up the-package (1.2.3ubuntu1-2-1) ...
Traceback (most recent call last):
File "/usr/lib/the-package/setup-package.py", line 3, in
from augeas import Augeas
File "/usr/lib/python2.7/dist-packages/augeas.py", line 78, in
class Augeas(object):
File "/usr/lib/python2.7/dist-packages/augeas.py", line 82, in Augeas
_libaugeas = _dlopen("augeas")
File "/usr/lib/python2.7/dist-packages/augeas.py", line 75, in _dlopen
raise ImportError("Unable to import lib%s!" % args[0])
ImportError: Unable to import libaugeas!
dpkg: error processing package the-package (--configure):
installed the-package package post-installation script subprocess returned
error exit status 1
Simply running apt-get -f install afterwards will succeed and run the postinst
script.
The cause of this problem seems to be that any invocations of `ldconfig` during
the installation of the dependent libraries, do nothing at all.
When adding `ldconfig -p >/tmp/ldconfig-output` to the postinst hook, one can
see that neither libaugeas0 nor any other libraries that were just installed,
are in the ldconfig cache at the moment the script is invoked.
Even when adding an explicit `ldconfig` in the postinst script before running
the python script, it still fails.
Very curiously, calling `ldconfig -v >/dev/null` instead, somehow makes
ldconfig work. This seems to indicate that there is some problem with I/O
redirection, but for some reason the `-v` is also essential.
** Affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Minimal example package that demonstrates the problem"
https://bugs.launchpad.net/bugs/1851675/+attachment/5303512/+files/the-package_1.2.3ubuntu1-2-1_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851675
Title:
dpkg fails to properly invoke ldconfig
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1851675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851676] [NEW] dmidecode decodes /sys/class/dmi/id/product_serial incorrectly
Public bug reported: Hi, On VMWare when decoding /sys/class/dmi/id/product_serial dmidecode produces an output whereby the first 16 characters have been reversed in comparison to /sys/class/dmi/id/product_uuid. This manifests itself by breaking provisioning in Kubernetes and could cause other issues down the line. Other OS such as redhat have already patched this in their releases. A demonstration of the issue can be found in this pastebin: https://pastebin.canonical.com/p/qRfrpHXwGs/ VMWare Issue: https://kb.vmware.com/s/article/53609 Cheers! ** Affects: dmidecode (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, On VMWare when decoding /sys/class/dmi/id/product_serial dmidecode produces an output whereby the first 16 characters have been reversed in comparison to /sys/class/dmi/id/product_uuid. - - This manifests itself by breaking provisioning in Kubernetes and could cause other issues down the line. Other OS such as redhat have already patched this in their releases. + This manifests itself by breaking provisioning in Kubernetes and could + cause other issues down the line. Other OS such as redhat have already + patched this in their releases. A demonstration of the issue can be found in this pastebin: https://pastebin.canonical.com/p/qRfrpHXwGs/ + VMWare Issue: https://kb.vmware.com/s/article/53609 + Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851676 Title: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1851676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850994] Re: ubuntu-aufs-modified mmap_region() breaks refcounting in overlayfs/shiftfs error path
** Description changed:
+ SRU Justification
+
+ Impact: overlayfs and shiftfs both replace vma->vm_file in their mmap
+ handlers. On error the original value is not restored, and the reference
+ is put for the file to which vm_file points. On upstream kernels this is
+ not an issue, as no callers dereference vm_file dereference vm_file
+ following after call_mmap() returns an error. However, the aufs patchs
+ change mmap_region() to replace the fput() using a local variable with
+ vma_fput(), which will fput() vm_file, leading to a refcount underflow.
+
+ Fix: Restore the original vma_file value on error.
+
+ Test Case: See below.
+
+ Regression Potential: Minimal. As stated above, other callers of
+ call_mmap() do not dereference vma->vm_file when it returns an error,
+ and the one which does is fixed by these patches.
+
+ Notes: Supported kernels prior to disco are not affected as overlayfs
+ did not support mmap until 4.19, and shiftfs was not present in Ubuntu
+ kernels before disco. The issue is mitigated for overlayfs by another
+ bug which is preventing unprivileged mounting; a patch for this issue
+ will be sent separately.
+
+ ---
+
Tested on 19.10.
Ubuntu's aufs kernel patch includes the following change (which I
interestingly
can't see in the AUFS code at
https://github.com/sfjro/aufs5-linux/blob/master/mm/mmap.c):
==
+#define vma_fput(vma) vma_do_fput(vma, __func__, __LINE__)
[...]
@@ -1847,8 +1847,8 @@ unsigned long mmap_region(struct file *file, unsigned
long addr,
- return addr;
-
- unmap_and_free_vma:
+ return addr;
+
+ unmap_and_free_vma:
+ vma_fput(vma);
- vma->vm_file = NULL;
+ vma->vm_file = NULL;
- fput(file);
-
- /* Undo any partial mapping done by a device driver. */
- unmap_region(mm, vma, prev, vma->vm_start, vma->vm_end);
+
+ /* Undo any partial mapping done by a device driver. */
+ unmap_region(mm, vma, prev, vma->vm_start, vma->vm_end);
[...]
+void vma_do_fput(struct vm_area_struct *vma, const char func[], int line)
+{
+ struct file *f = vma->vm_file, *pr = vma->vm_prfile;
+
+ prfile_trace(f, pr, func, line, __func__);
+ fput(f);
+ if (f && pr)
+ fput(pr);
+}
==
This means that in the case where call_mmap() returns an error to
mmap_region(),
fput() will be called on the current value of vma->vm_file instead of the
saved
file pointer. This matters if the ->mmap() handler replaces ->vm_file before
returning an error code.
overlayfs and shiftfs do that when call_mmap() on the lower filesystem fails,
see ovl_mmap() and shiftfs_mmap().
To demonstrate the issue, the PoC below mounts a shiftfs that is backed by a
FUSE filesystem with the FUSE flag FOPEN_DIRECT_IO, which causes
fuse_file_mmap()
to bail out with -ENODEV if MAP_SHARED is set.
I would have used overlayfs instead, but there is an unrelated bug that makes
it
impossible to mount overlayfs inside a user namespace:
Commit 82c0860106f264 ("UBUNTU: SAUCE: overlayfs: Propogate nosuid from lower
and upper mounts") defines SB_I_NOSUID as 0x0010, but SB_I_USERNS_VISIBLE
already has the same value. This causes mount_too_revealing() to bail out
with a
WARN_ONCE().
Note that this PoC requires the "bindfs" package and should be executed with
"slub_debug" in the kernel commandline to get a clear crash.
==
Ubuntu 19.10 user-Standard-PC-Q35-ICH9-2009 ttyS0
user-Standard-PC-Q35-ICH9-2009 login: user
- Password:
+ Password:
Last login: Fr Nov 1 23:45:36 CET 2019 on ttyS0
Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-19-generic x86_64)
- * Documentation: https://help.ubuntu.com
- * Management: https://landscape.canonical.com
- * Support:https://ubuntu.com/advantage
-
+ * Documentation: https://help.ubuntu.com
+ * Management: https://landscape.canonical.com
+ * Support:https://ubuntu.com/advantage
0 updates can be installed immediately.
0 of these updates are security updates.
user@user-Standard-PC-Q35-ICH9-2009:~$ ls
aufs-mmap Documents Music Public trace.dat
DesktopDownloads Pictures Templates Videos
user@user-Standard-PC-Q35-ICH9-2009:~$ cd aufs-mmap/
- user@user-Standard-PC-Q35-ICH9-2009:~/aufs-mmap$ cat /proc/cmdline
+ user@user-Standard-PC-Q35-ICH9-2009:~/aufs-mmap$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=f7d8d4fb-0c96-498e-b875-0b777127a332 ro console=ttyS0 slub_debug
quiet splash vt.handoff=7
user@user-Standard-PC-Q35-ICH9-2009:~/aufs-mmap$ cat run.sh
#!/bin/sh
sync
unshare -mUr ./run2.sh
user@user-Standard-PC-Q35-ICH9-2009:~/aufs-mmap$ cat run2.sh
#!/bin/bash
set -e
[Bug 1851499] Re: lz4 SIGSEGV in LZ4_decompress_generic
@Michail Do you have a full patch against e.g. disco sources / version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851499 Title: lz4 SIGSEGV in LZ4_decompress_generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lz4/+bug/1851499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851674] [NEW] All deb packages as being listed as "Proprietary" when opened in gnome-software
Public bug reported: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to happen from Ubuntu 18.04, with official and 3rd party packages (like those from virtualbox.org). ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
FYI discussed on KVM Forum and acknowledged that it is an issue. Discussion went to the ML then [1]. This essentially becomes an upstream-devel item to create some late- loading command as discussed there. But the impact and severity is rather low as the general thought is more like "yes an issue, but see (e)(f) on [2]. [1]: [1]: https://lists.gnu.org/archive/html/qemu-devel/2019-11/msg5.html [2]: https://lists.gnu.org/archive/html/qemu-devel/2019-11/msg00029.html ** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
I just discovered that on my laptop this bug only applies to X11 sessions, not to Wayland sessions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850774] Re: Crash when used in falkon as of 19.10
Sadly, no idea. The linked ticket provides no references unfortunately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850774 Title: Crash when used in falkon as of 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebengine-opensource-src/+bug/1850774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851682] [NEW] oscap is broken in ubuntu 19.10
Public bug reported: oscap segfaults while trying to check using ubuntu-security definitions: The command: oscap oval eval --report /tmp/oscap_report.html /var/tmp/com.ubuntu.eoan.cve.oval.xml Segfault: ... Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Probe with PID=26379 has been killed with signal 11 [../../../../../src/OVAL/probes/SEAP/sch_pipe.c:178] Probe with PID=26379 has core dumped. [../../../../../src/OVAL/probes/SEAP/sch_pipe.c:182] Unable to close probe sd [../../../src/OVAL/oval_probe_ext.c:424] Unable to receive a message from probe [../../../src/OVAL/oval_probe_ext.c:579] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] Probe with PID=26393 has been killed with signal 11 [../../../../../src/OVAL/probes/SEAP/sch_pipe.c:178] Probe with PID=26393 has core dumped. [../../../../../src/OVAL/probes/SEAP/sch_pipe.c:182] Unable to close probe sd [../../../src/OVAL/oval_probe_ext.c:424] Unable to receive a message from probe [../../../src/OVAL/oval_probe_ext.c:579] Invalid oval result type: -1. [../../../../src/OVAL/results/oval_resultTest.c:179] The OVAL definitions are taken directly from https://people.canonical.com/~ubuntu- security/oval/com.ubuntu.eoan.cve.oval.xml Version: oscap --version OpenSCAP command line tool (oscap) 1.2.16 Copyright 2009--2017 Red Hat Inc., Durham, North Carolina. Supported specifications XCCDF Version: 1.2 OVAL Version: 5.11.1 CPE Version: 2.3 CVSS Version: 2.0 CVE Version: 2.0 Asset Identification Version: 1.1 Asset Reporting Format Version: 1.1 CVRF Version: 1.1 Capabilities added by auto-loaded plugins SCE Version: 1.0 (from libopenscap_sce.so.8) Paths Schema files: /usr/share/openscap/schemas Default CPE files: /usr/share/openscap/cpe Probes: /usr/lib/x86_64-linux-gnu/openscap ** Affects: openscap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851682 Title: oscap is broken in ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openscap/+bug/1851682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
I really think you are all *way* over thinking this. a. growpart made a change to the partition table (using sfdisk) b. growpart called partx --update --nr 3 /dev/sda c. growpart exited With a and b growpart created udev events. If you create udev events, you really need to wait for those events to finish, or your just pushing complexity onto your consumer. Now Daniel's updated cloud-init with output captured in comment 14 clearly called udevadm settle after 'c'. But the problem still existed. So that means we have this sequence of events: a.) growpart change partition table b.) growpart call partx c.) udev created and events being processed d.) growpart exits e.) cloud-init calls udevadm settle f.) udev events occurring that removed the link g.) cloud-init raced on reading that size - fail To me, that means either udevadm settle called in 'e' didn't actually do what it is suppsoed to do and wait for all events in the queue to clear. Or, something else created new events. I have long suspected that to be the case, and I think the thing doing it is udev rules. If that is true, then udev events cause more udev events, so a single 'settle' is never enough. Nor can you actually ever know if you *have* settled long enough. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520874] Re: [MacBook8,1] keyboard does not work
@anomaly256: Could you please give a link to the bug report you filled? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520874 Title: [MacBook8,1] keyboard does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
> So that means we have this sequence of events: > a.) growpart change partition table > b.) growpart call partx > c.) udev created and events being processed That is not true. whilst sfdisk is deleting, creating, finishing partition table (a) and partx is called (b), udev events are already fired and running in parallel and may complete against deleted, partially new, completely new partition table, with or without partx completed. No amount of settling for events will fix the fact that events were run against racy state of the partition table _during_ sfdisk and partx calls. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851677] Re: s_iflags overlap prevents unprivileged overlayfs mounts
** Description changed: + SRU Justification + + Impact: SB_I_NOSUID was added by a sauce patch, and over time it has + come to occpy the same bit in s_iflags as SB_I_USERNS_VISIBLE without + being noticed. overlayfs will set SB_I_NOSUID when any lower mount is + nosuid. When this happens for a user namespace mount, + mount_too_revealing() will perform additional, unnecessary checks which + may block mounting when it should be allowed. + + Fix: Relocate SB_I_NOSUID to the top of s_iflags to remove the conflict + and to make future conflicts less likely. + + Test Case: Attached. + + Regression Potential: These flags are internal to the kernel, so moving + SB_I_NOSUID is safe. It's possible that the overlapping flags caused + other unintended behaviors, and if so these will also change and could + result in user-visible changes. However, any such behaviors would also + be incorrect. + + --- + As reported by Jann Horn on bug 1850994, unprivileged overlayfs mounting can fail in disco/eoan due to SB_I_NOSUID and SB_I_USERNS_VISIBLE. - overlayfs sets SB_I_NOSUID for unprivileged mounts, which causes + overlayfs sets SB_I_NOSUID in some cases, which causes mount_too_revealing() to see SB_I_USERNS_VISIBLE as being set. This leads to performing additional, unnecessary checks which may fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851677 Title: s_iflags overlap prevents unprivileged overlayfs mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
@ddstreet Yes, settle does not help. Re-triggering udevadm trigger --action=add /sys/class/block/sda Would re-run all of them after the partition change has occurred, which is what I'm currently suggesting as a heavy-handed workaround. I would like to understand *why* the udevd/kernel pair exhibits this racy behavior whereas other kernels/udevd from Bionic do not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850998] Re: package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
@lars, is this something that should be taken care of by the package during upgrades? ** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-8.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850998 Title: package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1850998/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850895] Re: package mysql-hostname-8.0 8.0.17-0ubuntu2 failed to install/upgrade: il sottoprocesso installato pacchetto mysql-hostname-8.0 script post-installation ha restituito lo stato di erro
@lars, is this something that should be taken care of by the package during upgrades? ** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850895 Title: package mysql-hostname-8.0 8.0.17-0ubuntu2 failed to install/upgrade: il sottoprocesso installato pacchetto mysql-hostname-8.0 script post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1850895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850895] Re: package mysql-hostname-8.0 8.0.17-0ubuntu2 failed to install/upgrade: il sottoprocesso installato pacchetto mysql-hostname-8.0 script post-installation ha restituito lo stato di erro
@lars, is this something that should be taken care of by the package during upgrades? ** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-8.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850895 Title: package mysql-hostname-8.0 8.0.17-0ubuntu2 failed to install/upgrade: il sottoprocesso installato pacchetto mysql-hostname-8.0 script post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1850895/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850998] Re: package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
@lars, is this something that should be taken care of by the package during upgrades? ** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850998 Title: package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1850998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851663] Re: Consistent autopkgtest failures on ppc64el/s390x
** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-disco ** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: Consistent autopkgtest failures on ppc64el/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851695] [NEW] DEP8 failure/regression in arm64 and armhf
Public bug reported: nspr 0.6.1~ds1-4 is failing DEP8 test in arm64 and armhf: autopkgtest [09:46:25]: test command1: /usr/bin/dh_golang_autopkgtest autopkgtest [09:46:25]: test command1: [--- [info] Testing github.com/theupdateframework/notary... [info] Source code installed by binary package, overriding dh_auto_configure... [info] Disabling existing override_dh_auto_configure... dh build --builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build \ --buildsystem=golang \ --with=golang dh_update_autotools_config -O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build -O--buildsystem=golang dh_autoreconf -O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build -O--buildsystem=golang debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' mkdir -p "_build" cp -a /usr/share/gocode/src "_build" make[1]: Leaving directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' debian/rules override_dh_auto_build make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' dh_auto_build -- -tags "pkcs11" cd _build && go install -gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -v -p 1 -tags pkcs11 github.com/theupdateframework/notary github.com/theupdateframework/notary/client github.com/theupdateframework/notary/client/changelist github.com/theupdateframework/notary/cmd/escrow github.com/theupdateframework/notary/cmd/notary github.com/theupdateframework/notary/cmd/notary-server github.com/theupdateframework/notary/cmd/notary-signer github.com/theupdateframework/notary/cryptoservice github.com/theupdateframework/notary/passphrase github.com/theupdateframework/notary/proto github.com/theupdateframework/notary/server github.com/theupdateframework/notary/server/errors github.com/theupdateframework/notary/server/handlers github.com/theupdateframework/notary/server/snapshot github.com/theupdateframework/notary/server/storage github.com/theupdateframework/notary/server/timestamp github.com/theupdateframework/notary/signer github.com/theupdateframework/notary/signer/api github.com/theupdateframework/notary/signer/client github.com/theupdateframework/notary/signer/keydbstore github.com/theupdateframework/notary/storage github.com/theupdateframework/notary/storage/rethinkdb github.com/theupdateframework/notary/trustmanager github.com/theupdateframework/notary/trustmanager/remoteks github.com/theupdateframework/notary/trustmanager/yubikey github.com/theupdateframework/notary/trustpinning github.com/theupdateframework/notary/tuf github.com/theupdateframework/notary/tuf/data github.com/theupdateframework/notary/tuf/signed github.com/theupdateframework/notary/tuf/testutils github.com/theupdateframework/notary/tuf/testutils/interfaces github.com/theupdateframework/notary/tuf/testutils/keys github.com/theupdateframework/notary/tuf/utils github.com/theupdateframework/notary/tuf/validation github.com/theupdateframework/notary/utils github.com/theupdateframework/notary/version src/github.com/docker/distribution/digestset/set.go:9:2: cannot find package "github.com/opencontainers/go-digest" in any of: /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/go-digest (vendor tree) /usr/lib/go-1.12/src/github.com/opencontainers/go-digest (from $GOROOT) /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/go-digest (from $GOPATH) src/github.com/docker/distribution/blobs.go:13:2: cannot find package "github.com/opencontainers/image-spec/specs-go/v1" in any of: /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/image-spec/specs-go/v1 (vendor tree) /usr/lib/go-1.12/src/github.com/opencontainers/image-spec/specs-go/v1 (from $GOROOT) /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/image-spec/specs-go/v1 (from $GOPATH) dh_auto_build: cd _build && go install -gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -v -p 1 -tags pkcs11 github.com/theupdateframework/notary github.com/theupdateframework/notary/client github.com/theupdateframework/notary/client/changelist github.com/theupdateframework/notary/cmd/escrow github.com/theupdateframework/notary/cmd/notary github.com/theupdateframework/notary/cmd/notary-server github.com/theupdateframework/notary/cmd/notary-signer github.com/theupdateframework/notary/cryptoservice github.com/theupdateframework/notary/passphrase github.com/theupdateframework/notary/proto github.com/theupdateframework/notary/server github.com/theupdateframework/notary/server/errors
[Bug 1851695] [NEW] DEP8 failure/regression in arm64 and armhf
Public bug reported: nspr 0.6.1~ds1-4 is failing DEP8 test in arm64 and armhf: autopkgtest [09:46:25]: test command1: /usr/bin/dh_golang_autopkgtest autopkgtest [09:46:25]: test command1: [--- [info] Testing github.com/theupdateframework/notary... [info] Source code installed by binary package, overriding dh_auto_configure... [info] Disabling existing override_dh_auto_configure... dh build --builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build \ --buildsystem=golang \ --with=golang dh_update_autotools_config -O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build -O--buildsystem=golang dh_autoreconf -O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build -O--buildsystem=golang debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' mkdir -p "_build" cp -a /usr/share/gocode/src "_build" make[1]: Leaving directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' debian/rules override_dh_auto_build make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp' dh_auto_build -- -tags "pkcs11" cd _build && go install -gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -v -p 1 -tags pkcs11 github.com/theupdateframework/notary github.com/theupdateframework/notary/client github.com/theupdateframework/notary/client/changelist github.com/theupdateframework/notary/cmd/escrow github.com/theupdateframework/notary/cmd/notary github.com/theupdateframework/notary/cmd/notary-server github.com/theupdateframework/notary/cmd/notary-signer github.com/theupdateframework/notary/cryptoservice github.com/theupdateframework/notary/passphrase github.com/theupdateframework/notary/proto github.com/theupdateframework/notary/server github.com/theupdateframework/notary/server/errors github.com/theupdateframework/notary/server/handlers github.com/theupdateframework/notary/server/snapshot github.com/theupdateframework/notary/server/storage github.com/theupdateframework/notary/server/timestamp github.com/theupdateframework/notary/signer github.com/theupdateframework/notary/signer/api github.com/theupdateframework/notary/signer/client github.com/theupdateframework/notary/signer/keydbstore github.com/theupdateframework/notary/storage github.com/theupdateframework/notary/storage/rethinkdb github.com/theupdateframework/notary/trustmanager github.com/theupdateframework/notary/trustmanager/remoteks github.com/theupdateframework/notary/trustmanager/yubikey github.com/theupdateframework/notary/trustpinning github.com/theupdateframework/notary/tuf github.com/theupdateframework/notary/tuf/data github.com/theupdateframework/notary/tuf/signed github.com/theupdateframework/notary/tuf/testutils github.com/theupdateframework/notary/tuf/testutils/interfaces github.com/theupdateframework/notary/tuf/testutils/keys github.com/theupdateframework/notary/tuf/utils github.com/theupdateframework/notary/tuf/validation github.com/theupdateframework/notary/utils github.com/theupdateframework/notary/version src/github.com/docker/distribution/digestset/set.go:9:2: cannot find package "github.com/opencontainers/go-digest" in any of: /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/go-digest (vendor tree) /usr/lib/go-1.12/src/github.com/opencontainers/go-digest (from $GOROOT) /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/go-digest (from $GOPATH) src/github.com/docker/distribution/blobs.go:13:2: cannot find package "github.com/opencontainers/image-spec/specs-go/v1" in any of: /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/image-spec/specs-go/v1 (vendor tree) /usr/lib/go-1.12/src/github.com/opencontainers/image-spec/specs-go/v1 (from $GOROOT) /tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/image-spec/specs-go/v1 (from $GOPATH) dh_auto_build: cd _build && go install -gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" -v -p 1 -tags pkcs11 github.com/theupdateframework/notary github.com/theupdateframework/notary/client github.com/theupdateframework/notary/client/changelist github.com/theupdateframework/notary/cmd/escrow github.com/theupdateframework/notary/cmd/notary github.com/theupdateframework/notary/cmd/notary-server github.com/theupdateframework/notary/cmd/notary-signer github.com/theupdateframework/notary/cryptoservice github.com/theupdateframework/notary/passphrase github.com/theupdateframework/notary/proto github.com/theupdateframework/notary/server github.com/theupdateframework/notary/server/errors
[Bug 1850969] Re: x11 session all mouse or keyboard action ignored
Problem disappeared after last upgrade: Start-Date: 2019-11-07 17:28:08 Commandline: apt upgrade Requested-By: corrado (1000) Upgrade: gir1.2-mutter-5:amd64 (3.34.1+git20191022-2ubuntu1, 3.34.1+git20191107-1ubuntu1), libmutter-5-0:amd64 (3.34.1+git20191022-2ubuntu1, 3.34.1+git20191107-1ubuntu1), mutter-common:amd64 (3.34.1+git20191022-2ubuntu1, 3.34.1+git20191107-1ubuntu1), mutter:amd64 (3.34.1+git20191022-2ubuntu1, 3.34.1+git20191107-1ubuntu1) End-Date: 2019-11-07 17:28:15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850969 Title: x11 session all mouse or keyboard action ignored To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
Arm64: $ grep NR_open $(dpkg -L linux-libc-dev | xargs) 2>/dev/null /usr/include/asm-generic/unistd.h:#define __NR_openat 56 /usr/include/asm-generic/unistd.h:__SYSCALL(__NR_openat, sys_openat) /usr/include/asm-generic/unistd.h:#define __NR_open_by_handle_at 265 /usr/include/asm-generic/unistd.h:__SYSCALL(__NR_open_by_handle_at, sys_open_by_handle_at) /usr/include/asm-generic/unistd.h:#define __NR_open_tree 428 /usr/include/asm-generic/unistd.h:__SYSCALL(__NR_open_tree, sys_open_tree) Amd64: $ grep NR_open $(dpkg -L linux-libc-dev | xargs) 2>/dev/null /usr/include/asm-generic/unistd.h:#define __NR_openat 56 /usr/include/asm-generic/unistd.h:__SYSCALL(__NR_openat, sys_openat) /usr/include/asm-generic/unistd.h:#define __NR_open_by_handle_at 265 /usr/include/asm-generic/unistd.h:__SYSCALL(__NR_open_by_handle_at, sys_open_by_handle_at) /usr/include/asm-generic/unistd.h:#define __NR_open_tree 428 /usr/include/asm-generic/unistd.h:__SYSCALL(__NR_open_tree, sys_open_tree) /usr/include/x86_64-linux-gnu/asm/unistd_32.h:#define __NR_open 5 /usr/include/x86_64-linux-gnu/asm/unistd_32.h:#define __NR_openat 295 /usr/include/x86_64-linux-gnu/asm/unistd_32.h:#define __NR_open_by_handle_at 342 /usr/include/x86_64-linux-gnu/asm/unistd_32.h:#define __NR_open_tree 428 /usr/include/x86_64-linux-gnu/asm/unistd_64.h:#define __NR_open 2 /usr/include/x86_64-linux-gnu/asm/unistd_64.h:#define __NR_openat 257 /usr/include/x86_64-linux-gnu/asm/unistd_64.h:#define __NR_open_by_handle_at 304 /usr/include/x86_64-linux-gnu/asm/unistd_64.h:#define __NR_open_tree 428 /usr/include/x86_64-linux-gnu/asm/unistd_x32.h:#define __NR_open (__X32_SYSCALL_BIT + 2) /usr/include/x86_64-linux-gnu/asm/unistd_x32.h:#define __NR_openat (__X32_SYSCALL_BIT + 257) /usr/include/x86_64-linux-gnu/asm/unistd_x32.h:#define __NR_open_by_handle_at (__X32_SYSCALL_BIT + 304) /usr/include/x86_64-linux-gnu/asm/unistd_x32.h:#define __NR_open_tree (__X32_SYSCALL_BIT + 428) So this really might be different on arm, not sure what to do about it yet. Might be related to https://github.com/seccomp/libseccomp/commit/0db8babb27eed3ce202d54ec1cd99f23367631cf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849785 Title: FTBFS on i386/ppc64/s390x (Eoan+Focal) To manage notifications about this bug go to: https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)
Build issue is reproducible on arm64 LP infrastructure builds. I spawned a canonistack arm64 system to check if it is reproducible there as well for some debugging how we could fix it. Interestingly, it does NOT FAIL on focal as-is when building on aarch64. But as LP builds are against -proposed I Then switched to focal-proposed which upgraded this list of things: apport/focal-proposed 2.20.11-0ubuntu11 all [upgradable from: 2.20.11-0ubuntu9] fwupd-signed/focal-proposed 1.12+1.3.3-2 arm64 [upgradable from: 1.10+1.2.10-1ubuntu2] fwupd/focal-proposed 1.3.3-2 arm64 [upgradable from: 1.2.10-1ubuntu2] gawk/focal-proposed 1:5.0.1+dfsg-1 arm64 [upgradable from: 1:4.2.1+dfsg-1.1build1] libcap2-bin/focal-proposed 1:2.27-1 arm64 [upgradable from: 1:2.25-2] libcap2/focal-proposed 1:2.27-1 arm64 [upgradable from: 1:2.25-2] libdebconfclient0/focal-proposed 0.250ubuntu1 arm64 [upgradable from: 0.249ubuntu1] libfwupd2/focal-proposed 1.3.3-2 arm64 [upgradable from: 1.2.10-1ubuntu2] libglib2.0-0/focal-proposed 2.63.1-1 arm64 [upgradable from: 2.62.1-1] libglib2.0-bin/focal-proposed 2.63.1-1 arm64 [upgradable from: 2.62.1-1] libglib2.0-data/focal-proposed 2.63.1-1 all [upgradable from: 2.62.1-1] liblz4-1/focal-proposed 1.9.2-1 arm64 [upgradable from: 1.9.1-2] libpam-cap/focal-proposed 1:2.27-1 arm64 [upgradable from: 1:2.25-2] libpython3-all-dev/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1] libpython3-dev/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1] libpython3-stdlib/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1] libseccomp2/focal-proposed 2.4.1-0ubuntu0.19.10.4 arm64 [upgradable from: 2.4.1-0ubuntu0.19.10.3] linux-headers-generic/focal-proposed 5.3.0.21.24 arm64 [upgradable from: 5.3.0.19.22] linux-headers-virtual/focal-proposed 5.3.0.21.24 arm64 [upgradable from: 5.3.0.19.22] linux-image-virtual/focal-proposed 5.3.0.21.24 arm64 [upgradable from: 5.3.0.19.22] linux-libc-dev/focal-proposed 5.3.0-21.22 arm64 [upgradable from: 5.3.0-19.20] linux-virtual/focal-proposed 5.3.0.21.24 arm64 [upgradable from: 5.3.0.19.22] lz4/focal-proposed 1.9.2-1 arm64 [upgradable from: 1.9.1-2] python3-all-dev/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1] python3-all/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1] python3-apport/focal-proposed 2.20.11-0ubuntu11 all [upgradable from: 2.20.11-0ubuntu9] python3-colorama/focal-proposed 0.4.1-1 all [upgradable from: 0.3.7-1] python3-dev/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1] python3-distupgrade/focal-proposed 1:20.04.4 all [upgradable from: 1:20.04.2] python3-jwt/focal-proposed 1.7.1-2 all [upgradable from: 1.7.1-1] python3-launchpadlib/focal-proposed 1.10.7-2 all [upgradable from: 1.10.7-1] python3-lazr.restfulclient/focal-proposed 0.14.2-2 all [upgradable from: 0.14.2-1] python3-lazr.uri/focal-proposed 1.0.3-4 all [upgradable from: 1.0.3-3] python3-minimal/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1] python3-oauthlib/focal-proposed 3.1.0-1 all [upgradable from: 2.1.0-1] python3-pkg-resources/focal-proposed 41.4.0-1 all [upgradable from: 41.1.0-1] python3-problem-report/focal-proposed 2.20.11-0ubuntu11 all [upgradable from: 2.20.11-0ubuntu9] python3-twisted-bin/focal-proposed 18.9.0-4 arm64 [upgradable from: 18.9.0-3ubuntu1] python3-twisted/focal-proposed 18.9.0-4 all [upgradable from: 18.9.0-3ubuntu1] python3-wadllib/focal-proposed 1.3.3-3 all [upgradable from: 1.3.3-2] python3/focal-proposed 3.7.5-1ubuntu1 arm64 [upgradable from: 3.7.5-1] ubuntu-release-upgrader-core/focal-proposed 1:20.04.4 all [upgradable from: 1:20.04.2] I especially wanted to check linux-libc-dev as that brings the headers used here: That 5.3.0-19.20 is actually newer and just in the image. There is a 5.3.0-18.19 from http://us.ports.ubuntu.com/ubuntu-ports focal/main. So maybe instead of upgrading the trigger is downgrading to that? Fail: LP build (two days ago): 5.3.0-18.19 Fail: LP build (rebuild today): 5.3.0-18.19 Good: canonistack (focal image): 5.3.0-19.20 Good: canonistack (focal-proposed): 5.3.0-21.22 Good: canonistack (focal-release): 5.3.0-18.19 This isn't very insightful, it just always works except in LP builders :-/ The difference in the package version, even when rebuilding is odd, but at least in the tests wasn't the reason. For now I'm scratching my head and will hit rebuild tomorrow again ... ?! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849785 Title: FTBFS on i386/ppc64/s390x (Eoan+Focal) To manage notifications about this bug go to: https://bugs.launchpad.net/libseccomp/+bug/1849785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851507] Re: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker
** 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Thursday, 07. November 2019 14:02 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851507 Title: bionic/linux-oem: 4.15.0-1062.71 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
Just curious, did anyone actually test with my suggestion from comment 40? That is, just make your partition table change (and update the kernel with partx or whatever, of course), and after it's done trigger --settle udev for the device. Be interesting to know if that actually fixes it or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849431] Re: Discover fashion style
** Package changed: apache2 (Ubuntu) => null-and-void ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849431 Title: Discover fashion style To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1849431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849330] Re: SHOES
** Package changed: apache2 (Ubuntu) => null-and-void ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849330 Title: SHOES To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1849330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
The feature works now. You might want to release it earlier than 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849331] Re: Trendy sneakers
** Package changed: apache2 (Ubuntu) => null-and-void ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849331 Title: Trendy sneakers To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1849331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /
This bug has a lot of troubleshooting comments, but lacks a good summary
about what is going on. I don't expect the xenial installer to be
changed anymore, short of critical bugs affecting it.
@tcstone, you say you hit something similar with 18.04.2. Current bionic
release is 18.04.3, would you mind to try again, and if you still hit a
bug, file a new one please? Please note that the default server install
in bionic is subiquity ("live-server"), and bugs against that should be
filed via https://bugs.launchpad.net/subiquity/+filebug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851696] [NEW] DEP8 failure with new lz4
Public bug reported: There are DEP8 failures with the new lz4 package on focal-proposed, 1.9.2-1 [ 78%] main.mysqlpump_basic_lz4 [ fail ] Test ended at 2019-11-04 20:04:36 CURRENT_TEST: main.mysqlpump_basic_lz4 Dump progress: 1/2 tables, 0/9 rows mysqlpump: [NOTE] (1585) This function 'format_bytes' has the same name as a native function mysqlpump: [WARNING] (3719) 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. mysqlpump: [WARNING] (3719) 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. Dump completed in 1347 /tmp/tmp.W8GeexahTr/ : decoded 2515 bytes --- /usr/lib/mysql-test/r/mysqlpump_basic_lz4.result2019-06-25 13:23:30.0 +0300 +++ /tmp/tmp.W8GeexahTr/var/log/mysqlpump_basic_lz4.reject 2019-11-04 23:04:36.722724150 +0300 @@ -1,3 +1,4 @@ +*** LZ4 command line interface 64-bits v1.9.2, by Yann Collet *** CREATE DATABASE bug21644479_lz4; USE bug21644479_lz4; CREATE TABLE t1 (a INT); mysqltest: Result content mismatch safe_process[30900]: Child process: 30901, exit: 1 - the logfile can be found in '/tmp/tmp.W8GeexahTr/var/log/main.mysqlpump_basic_lz4/mysqlpump_basic_lz4.log' Retrying test main.mysqlpump_basic_lz4, attempt(2/3). [ 78%] main.mysqlpump_basic_lz4 [ retry-fail ] Test ended at 2019-11-04 20:04:40 CURRENT_TEST: main.mysqlpump_basic_lz4 Dump progress: 1/2 tables, 0/9 rows mysqlpump: [NOTE] (1585) This function 'format_bytes' has the same name as a native function mysqlpump: [WARNING] (3719) 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. mysqlpump: [WARNING] (3719) 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. Dump completed in 1417 /tmp/tmp.W8GeexahTr/ : decoded 2515 bytes --- /usr/lib/mysql-test/r/mysqlpump_basic_lz4.result2019-06-25 13:23:30.0 +0300 +++ /tmp/tmp.W8GeexahTr/var/log/mysqlpump_basic_lz4.reject 2019-11-04 23:04:40.454636089 +0300 @@ -1,3 +1,4 @@ +*** LZ4 command line interface 64-bits v1.9.2, by Yann Collet *** CREATE DATABASE bug21644479_lz4; USE bug21644479_lz4; CREATE TABLE t1 (a INT); mysqltest: Result content mismatch safe_process[30960]: Child process: 30961, exit: 1 - the logfile can be found in '/tmp/tmp.W8GeexahTr/var/log/main.mysqlpump_basic_lz4/mysqlpump_basic_lz4.log' Test main.mysqlpump_basic_lz4 has failed 2 times, no more retries. ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-8.0 in Ubuntu. https://bugs.launchpad.net/bugs/1851696 Title: DEP8 failure with new lz4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1851696/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /
This bug has a lot of troubleshooting comments, but lacks a good summary
about what is going on. I don't expect the xenial installer to be
changed anymore, short of critical bugs affecting it.
@tcstone, you say you hit something similar with 18.04.2. Current bionic
release is 18.04.3, would you mind to try again, and if you still hit a
bug, file a new one please? Please note that the default server install
in bionic is subiquity ("live-server"), and bugs against that should be
filed via https://bugs.launchpad.net/subiquity/+filebug.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1740026] Re: ubiquity crashed with UnicodeDecodeError in decode(): 'utf-8' codec can't decode byte 0x91 in position 269: invalid start byte
Digging a little deeper, specifically in /usr/lib/ubiquity/plugins/ubi- prepare.py, in the method setup_sufficient_space() there is a call to a subprocess, that subprocess being parted_devices. Running parted_devices on your own in terminal with this device will report the above "HBG4a" and unicode character, but since this is not UTF8 I think the python script will fail since the default stance on errors is to fail with an error code, UnicodeDecodeError(). To bypass this, I modified that call to be as such: proc = subprocess.Popen(['parted_devices'], stdout=subprocss.PIPE, encoding='iso-8859-1', universal_newlines=True) This allows it to at least get passed this reported error. But subsequently, it will fail on ubi-partman.py with error code 141 (unknown what it means), and will not enter the partition manager in ubiquity (skips it entirely). The problem seems that this unicode naming keeps coming back to haunt the python scripts as it attempts to run the partition manager. Ideally, it would be great to remove this unicode in the name entirely since I don't think it will affect the partitioning in any way (I even looked into where the hardware reports this from and if it can be manually changed, but so far no dice). Otherwise, I'm stuck with hunting through all the scripts that do these calls and reads from the name and patch them to work with the iso-8859-1 encoding. Onward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740026 Title: ubiquity crashed with UnicodeDecodeError in decode(): 'utf-8' codec can't decode byte 0x91 in position 269: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1740026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851676] Re: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly
** Description changed: Hi, - On VMWare when decoding /sys/class/dmi/id/product_serial dmidecode - produces an output whereby the first 16 characters have been reversed in - comparison to /sys/class/dmi/id/product_uuid. + On VMWare 6.5 and higher (HW version 13 and higher) when decoding + /sys/class/dmi/id/product_serial dmidecode produces an output whereby + the first 16 characters have been reversed in comparison to + /sys/class/dmi/id/product_uuid. This manifests itself by breaking provisioning in Kubernetes and could cause other issues down the line. Other OS such as redhat have already patched this in their releases. A demonstration of the issue can be found in this pastebin: https://pastebin.canonical.com/p/qRfrpHXwGs/ VMWare Issue: https://kb.vmware.com/s/article/53609 Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851676 Title: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1851676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
