[Bug 1836030] Re: enable realtek ethernet device ASPM function
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Focal) Importance: Undecided Status: Fix Released ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux-oem-osp1 (Ubuntu Focal) ** Changed in: linux (Ubuntu Focal) Status: New => 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/1836030 Title: enable realtek ethernet device ASPM function To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718850] Re: Mode extensions appear off by default
@Jeremy I hope this warning in Ubuntu 19.10 is not a problem:- pranav@exam:~$ gnome-shell-extension-prefs (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.409: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.409: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61900. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.409: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.409: The offending signal was destroy on Gjs_ExtensionRow 0x55eba4152690. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61c00. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61600. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.410: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61f00. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.411: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.411: The offending signal was destroy on Gjs_ExtensionRow 0x55eba4152390. == Stack trace for context 0x55eba37d71a0 == (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.411: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-shell-extension-prefs:21099): Gjs-CRITICAL **: 12:46:15.411: The offending signal was destroy on Gjs_ExtensionRow 0x55eba3f61300. == Stack trace for context 0x55eba37d71a0 == pranav@exam:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718850 Title: Mode extensions appear off by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1718850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865109] Re: bionic/linux: 4.15.0-91.92 -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: Saturday, 29. February 2020 01:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1865269 bionic/linux-fips: bug 1865203 bionic/linux-gke-4.15: bug 1865255 bionic/linux-ibm-gt: bug 1865201 - bionic/linux-kvm: bug 1865247, bug 1864737 + bionic/linux-kvm: bug 1864737, bug 1865247 bionic/linux-oem: bug 1865200 - bionic/linux-oracle: bug 1865480, bug 1863339 + bionic/linux-oracle: bug 1863339, bug 1865480 bionic/linux-raspi2: bug 1864726 bionic/linux-snapdragon: bug 1864729 bionic/linux/pc-kernel: bug 1865107 bionic/linux/pc-lowlatency-kernel: bug 1865108 xenial/linux-azure: bug 1865198 xenial/linux-gcp: bug 1865251 xenial/linux-hwe: bug 1865142 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/1865109 Title: bionic/linux: 4.15.0-91.92 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865851] Re: pcmanfm-qt item selection feature in single-click mode
How would you make the first selection without activating the item? Currently what I do is right click on the entry--resulting in a popup menu--and then right click again to remove the menu. There is no other place to left click to make the first selection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865851 Title: pcmanfm-qt item selection feature in single-click mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1865851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -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: 1865109 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 03. March 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-aws-fips: bug 1864732, bug 1865419 + bionic/linux-aws-fips: bug 1865419, bug 1864732 bionic/linux-aws/aws-kernel: bug 1865268 xenial/linux-aws-hwe: bug 1865421 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/1865269 Title: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866506] Re: not able to use advance touchpad
Hi, what do you mean by "Advanced mode"? Could you also attach dmesg log when it's working in that non-advanced mode? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866506 Title: not able to use advance touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865855] Re: Network configuration does not allow importion of vpn configuration
I added the package network-manager-openvpn and now using the ConnectionManager I can find the option to load a configuration from file. The issue now is that it does not allow me to save the entry. Could you tell me where I should report this bug? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865855 Title: Network configuration does not allow importion of vpn configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1865855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861379] Re: Boot log is swamped with "debugfs: Directory 'imc' with parent 'powerpc' already present" messages on kernel 5.4
The commit got applied to "Ubuntu-5.4-5.4.0-14.17" and that's also the version that's currently in focal's release pocket: "linux-generic | 5.4.0.14.17 | focal | s390x". Hence changing the status of this ticket to Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-power-systems 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/1861379 Title: Boot log is swamped with "debugfs: Directory 'imc' with parent 'powerpc' already present" messages on kernel 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866377] Re: update-initramfs fails on plymouth hook due to missing target dir
I confirm that it is fixed on Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866377 Title: update-initramfs fails on plymouth hook due to missing target dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1866377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
I upload 02.18.85-0.3ubuntu2~p1 (focal) to https://launchpad.net /~ycheng-twn/+archive/ubuntu/lshw and it works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866162] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-03-09 04:15 EDT--- This has now been merged in Linus' upstream tree as df057c914a9c219ac8b8ed22caf7da2f80c1fe26 s390/pci: Fix unexpected write combine on resource -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866162 Title: [UBUNTU 20.04] ZPCI used write back addresses by default but should use write through To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866162] Re: [UBUNTU 20.04] ZPCI used write back addresses by default but should use write through
Hi Niklas, yes, thx. Also found the patch in 'linux-next' and cherry-picked that one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866162 Title: [UBUNTU 20.04] ZPCI used write back addresses by default but should use write through To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc5/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865517] Re: cannot log in with long username
By the way : user.lastnamelastnamelastn...@domain.fr does not trigger the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865517 Title: cannot log in with long username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1865517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865517] Re: cannot log in with long username
Just retried with fresh download of this file : http://cdimage.ubuntu.com/daily-live/current/focal-desktop-amd64.iso I confirm that entering on tty3 username.lastnamelastnamelastn...@domain.fr (not just "user.") does trigger the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865517 Title: cannot log in with long username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1865517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866604] [NEW] gdbtui source window does't display Unicode text
Public bug reported:
In Ubuntu 20.04, I discovered that the gdb 9 TUI source code window
doesn't display properly the UTF-8 characters (Chinese, Cyrillic, etc.)
but displays correctly only the ASCII ones. For example, the following
source code
printf("Здравей, свят!\n");
appears in the source code window as
printf("^^P^ ^P^ ^Q^┗↑@^^P^ ^P^ ^P^ ^P^ ^^Q^┗↑╝^^P^ ^Q^ ^Q^ \n");
The command windows is not affected (when I type non-ASCII characters
into it, they appear OK).
Additionally, I found out the following:
(1) This bug was introduced in version 8.3;
(2) It affects only some CPU architectures.
In more detail, I tested version "Debian 8.3.1-1" on two 64-bit machines
with the same version of Debian (bullseye/sid), one with PowerPC, and
the other with SPARC. The bug shows up only on the SPARC machine, not
the PowerPC one. I then built the generic version 8.3.1 on a 64-bit ARM
machine. The bug didn't show up there. And then, I built it on a 64-bit
MIPS (big endian) machine, where the bug did show up. Repeated this with
version 8.3. The bug showed up again. When I built the generic version
8.2.1 on the same MIPS machine, the bug didn't show up. A "diff -u
gdb-8.2.1/gdb/tui gdb-8.3/gdb/tui" shows a lot of changes made in the
TUI code of version 8.3 to add some colourisation to the TUI, and the
bug was probably introduced during this process. Sorry that I can't help
more to isolate the bug. But it's quite strange that it manifests itself
only on x86-64 (as I had found out previously using Ubuntu 20-04), SPARC
and MIPS, but not on ARM and PowerPC. I suppose that because of this, it
will be rather hard to pinpoint.
This bug is similar to the already fixed bug 1275210 where I also
described it but then realised that it has a different origin and is
therefore a different bug, so I report it as a new one now. Someone
already reported this bug as bug 25296 in the gdb Bugzilla which I
confirmed there.
** Affects: gdb (Ubuntu)
Importance: Undecided
Status: New
** Tags: gdb gdbtui utf-8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866604
Title:
gdbtui source window does't display Unicode text
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1866604/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866535] Re: Ubuntu Server 19.10 installer uses wrong NVMe path for Samsung 970 EVO Plus M.2 SSD (could not stat device - failed to find device at path)
** Package changed: debian-installer (Ubuntu) => subiquity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866535 Title: Ubuntu Server 19.10 installer uses wrong NVMe path for Samsung 970 EVO Plus M.2 SSD (could not stat device - failed to find device at path) To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3
I can still reproduce this issue with kernel mentioned in comment#17. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865245] Re: xenial/linux-aws: 4.4.0-1104.115 -proposed tracker
4.4.0-1104.115 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): tsc - failed on c5.metal (bug 1851607) ubuntu_kernel_selftests - cpu_hotplug (bug 1812149) on t2.small ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) vmx (bug 1821394) vmx_apic_passthrough_thread (bug 1822309) vmx_apicv_test (bug 1827866) vmx_eoi_bitmap_ioapic_scan (bug 1860515) vmx_hlt_with_rvi_test (bug 1822308) on bare metal nodes ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify07 blacklisted (bug 1775165) fanotify10 (bug 1802454) move_pages12 (bug 1831043) on some instances fallocate06 (bug 1865967) kill11 (bug 1865965) q uotactl07 (bug 1864092) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Skipped / blacklisted: * ubuntu_ltp * ubuntu_sysdig_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865245 Title: xenial/linux-aws: 4.4.0-1104.115 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865245] Re: xenial/linux-aws: 4.4.0-1104.115 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865245 Title: xenial/linux-aws: 4.4.0-1104.115 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865266] Re: Gwenview installl plugins doesnt work
kipi-plugins is now in 'NEW' in the upload queue: https://launchpad.net/ubuntu/focal/+queue?queue_state=0&queue_text= needing to be approved by an archive admin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865266 Title: Gwenview installl plugins doesnt work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1865266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865245] Re: xenial/linux-aws: 4.4.0-1104.115 -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: 1865106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 02. March 2020 10:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1865244 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/1865245 Title: xenial/linux-aws: 4.4.0-1104.115 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865109] Re: bionic/linux: 4.15.0-91.92 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/9BScF8ij/311-bionic-linux- image-4150-91-generic-4150-9192 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1865109 Title: bionic/linux: 4.15.0-91.92 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865200 Title: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865140] Re: bionic/linux-hwe-5.0: 5.0.0-43.47~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => 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/1865140 Title: bionic/linux-hwe-5.0: 5.0.0-43.47~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865109] Re: bionic/linux: 4.15.0-91.92 -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: Saturday, 29. February 2020 01:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1865269 bionic/linux-fips: bug 1865203 bionic/linux-gke-4.15: bug 1865255 bionic/linux-ibm-gt: bug 1865201 bionic/linux-kvm: bug 1864737, bug 1865247 bionic/linux-oem: bug 1865200 - bionic/linux-oracle: bug 1863339, bug 1865480 + bionic/linux-oracle: bug 1865480, bug 1863339 bionic/linux-raspi2: bug 1864726 bionic/linux-snapdragon: bug 1864729 bionic/linux/pc-kernel: bug 1865107 bionic/linux/pc-lowlatency-kernel: bug 1865108 xenial/linux-azure: bug 1865198 xenial/linux-gcp: bug 1865251 xenial/linux-hwe: bug 1865142 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/1865109 Title: bionic/linux: 4.15.0-91.92 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865139] Re: bionic/linux-hwe: 5.3.0-42.34~18.04.1 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/WXwqnT66/313-bionic-hwe-linux- image-530-42-generic-530-423418041 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1865139 Title: bionic/linux-hwe: 5.3.0-42.34~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865139] Re: bionic/linux-hwe: 5.3.0-42.34~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: 1865111 packages: lrm: linux-restricted-modules-hwe main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Sunday, 01. March 2020 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff 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/1865139 Title: bionic/linux-hwe: 5.3.0-42.34~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -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: 1865109 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Ready for Promote to Proposed - phase-changed: Monday, 09. March 2020 03:04 UTC + phase: Promote to Proposed + phase-changed: Monday, 09. March 2020 09:06 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- review 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/1865200 Title: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1202122] Re: autopilot ubiquity
** Changed in: ubiquity (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1202122 Title: autopilot ubiquity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1202122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865142] Re: xenial/linux-hwe: 4.15.0-91.92~16.04.1 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/A3bmA6Zs/314-xenial-hwe-linux- image-4150-91-generic-4150-919216041 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1865142 Title: xenial/linux-hwe: 4.15.0-91.92~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863324] Re: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: rpi2-armhf: https://certification.canonical.com/hardware/201906-27188/submission/163237/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1863324 Title: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865142] Re: xenial/linux-hwe: 4.15.0-91.92~16.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: 1865109 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Sunday, 01. March 2020 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1865495 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/1865142 Title: xenial/linux-hwe: 4.15.0-91.92~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863324] Re: xenial/linux-raspi2: 4.4.0-1130.139 -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: 1865106 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 20. February 2020 16:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1863322 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/1863324 Title: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863268] Re: bionic/linux-raspi2-5.3: 5.3.0-1019.21~18.04.1 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: Rpi2b-armhf: https://certification.canonical.com/hardware/201906-27188/submission/162883/ Rpi3b-arm64: https://certification.canonical.com/hardware/201811-26649/submission/162885/ Rpi3b-armhf: https://certification.canonical.com/hardware/201811-26649/submission/162879/ Rpi3a+-arm64: https://certification.canonical.com/hardware/201901-26785/submission/162884/ Rpi3a+-armhf: https://certification.canonical.com/hardware/201901-26785/submission/162878/ Rpi3b+-arm64: https://certification.canonical.com/hardware/201810-26542/submission/162882/ Rpi3b+-armhf: https://certification.canonical.com/hardware/201810-26542/submission/162877/ Rpi4b-1g-arm64: https://certification.canonical.com/hardware/201911-27471/submission/162869/ Rpi4b-1g-armhf: https://certification.canonical.com/hardware/201910-27407/submission/162875/ Rpi4b-2g-arm64: https://certification.canonical.com/hardware/201911-27507/submission/162870/ Rpi4b-2g-armhf: https://certification.canonical.com/hardware/201911-27506/submission/162874/ Rpi4b-4g-arm64: https://certification.canonical.com/hardware/201911-27456/submission/162871/ Rpi4b-4g-armhf: https://certification.canonical.com/hardware/201911-27455/submission/162872/ CM3-arm64: Unable to test, no space to upgrade kernel CM3-armhf: Unable to test, no space to upgrade kernel CM3+-arm64: https://certification.canonical.com/hardware/201908-27277/submission/162881/ CM3+-armhf: https://certification.canonical.com/hardware/201908-27277/submission/162876/ ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1863268 Title: bionic/linux-raspi2-5.3: 5.3.0-1019.21~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864071] Update Released
The verification of the Stable Release Update for libreoffice 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/1864071 Title: [SRU] libreoffice 6.3.5 for eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1864071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864071] Re: [SRU] libreoffice 6.3.5 for eoan
This bug was fixed in the package libreoffice - 1:6.3.5-0ubuntu0.19.10.1 --- libreoffice (1:6.3.5-0ubuntu0.19.10.1) eoan; urgency=medium * New upstream release (LP: #1864071) -- Heather Ellsworth Wed, 19 Feb 2020 09:30:23 -0700 ** Changed in: libreoffice (Ubuntu Eoan) 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/1864071 Title: [SRU] libreoffice 6.3.5 for eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1864071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866486] Re: focal/linux-kvm: 5.4.0-1004.4 -proposed tracker
** Summary changed: - focal/linux-kvm: -proposed tracker + focal/linux-kvm: 5.4.0-1004.4 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati (p-pisati) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866486 Title: focal/linux-kvm: 5.4.0-1004.4 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863268] Re: bionic/linux-raspi2-5.3: 5.3.0-1019.21~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: 1863269 packages: main: linux-raspi2-5.3 meta: linux-meta-raspi2-5.3 phase: Testing phase-changed: Tuesday, 18. February 2020 23:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2-5.3/pi-kernel: bug 1863267 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/1863268 Title: bionic/linux-raspi2-5.3: 5.3.0-1019.21~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
** Changed in: intel-microcode (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823655] Re: Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work
As mentioned on IRC, going forward there will only be a single channel 18-pi. Also, since this problem is resolved in the 5.x kernel, I'm going to mark this bug as resolved. If someone needs this with the 4.15 kernel or with core16, please open a new ticket and we'll evaluate it. ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => 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/1823655 Title: Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1823655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863669] Re: update to docker 19.03.6 and runc 1.0.0-rc10
This bug was fixed in the package runc - 1.0.0~rc10-0ubuntu1~19.10.1 --- runc (1.0.0~rc10-0ubuntu1~19.10.1) eoan; urgency=medium * Backport to eoan. (LP: #1863669, CVE-2019-19921) -- Michael Hudson-Doyle Wed, 19 Feb 2020 14:03:26 +1300 ** Changed in: runc (Ubuntu Eoan) 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/1863669 Title: update to docker 19.03.6 and runc 1.0.0-rc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1863669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863669] Update Released
The verification of the Stable Release Update for docker.io 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/1863669 Title: update to docker 19.03.6 and runc 1.0.0-rc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1863669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866486] Re: focal/linux-kvm: 5.4.0-1004.4 -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: 1866488 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Packaging - phase-changed: Sunday, 08. March 2020 03:08 UTC + phase: Packaging + phase-changed: Monday, 09. March 2020 09:31 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded 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/1866486 Title: focal/linux-kvm: 5.4.0-1004.4 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866568] Re: nova-novncproxy service can't start on ussuri-proposed
** Changed in: charm-nova-cloud-controller Status: New => Invalid ** Also affects: nova (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/1866568 Title: nova-novncproxy service can't start on ussuri-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1866568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862846] Update Released
The verification of the Stable Release Update for util-linux 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/1862846 Title: Crash and failure installing focal To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862846] Re: Crash and failure installing focal
This bug was fixed in the package util-linux - 2.34-0.1ubuntu2.3 --- util-linux (2.34-0.1ubuntu2.3) eoan; urgency=medium * d/p/lsblk-force-to-print-PKNAME-for-partition.patch: fix regression that lsblk doesn't print PKNAME column for partitions (LP: #1862846) -- Mauricio Faria de Oliveira Thu, 20 Feb 2020 11:13:53 -0300 ** Changed in: util-linux (Ubuntu Eoan) 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/1862846 Title: Crash and failure installing focal To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858776] Re: Intel Bluetooth AX201 HarrisonPeak (HrP) [8086:06f0] subsystem [8086:4070] firmware causes system hang in deep suspend
** Changed in: hwe-next Status: New => 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/1858776 Title: Intel Bluetooth AX201 HarrisonPeak (HrP) [8086:06f0] subsystem [8086:4070] firmware causes system hang in deep suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863664] Re: can't add users to quassel
This bug was fixed in the package quassel - 1:0.13.1-1ubuntu1.19.10.1 --- quassel (1:0.13.1-1ubuntu1.19.10.1) eoan; urgency=medium * Cherry-pick fix introduced in Debian in revision 1:0.13.1-2 to fix apparmor profile (LP: #1863664) -- Gianfranco Costamagna Mon, 17 Feb 2020 19:02:52 +0100 ** Changed in: quassel (Ubuntu Eoan) 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/1863664 Title: can't add users to quassel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1863664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863664] Update Released
The verification of the Stable Release Update for quassel 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/1863664 Title: can't add users to quassel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1863664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863669] Re: update to docker 19.03.6 and runc 1.0.0-rc10
This bug was fixed in the package docker.io - 19.03.6-0ubuntu1~18.04.1 --- docker.io (19.03.6-0ubuntu1~18.04.1) bionic; urgency=medium * Backport to Bionic (LP: #1863669) * Bootstrap Go 1.12.17 as part of the build. -- Michael Hudson-Doyle Wed, 19 Feb 2020 14:06:16 +1300 ** Changed in: docker.io (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/1863669 Title: update to docker 19.03.6 and runc 1.0.0-rc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1863669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836987] Re: update to 18.09.8
This bug was fixed in the package docker.io - 19.03.6-0ubuntu1~18.04.1 --- docker.io (19.03.6-0ubuntu1~18.04.1) bionic; urgency=medium * Backport to Bionic (LP: #1863669) * Bootstrap Go 1.12.17 as part of the build. -- Michael Hudson-Doyle Wed, 19 Feb 2020 14:06:16 +1300 ** Changed in: docker.io (Ubuntu Bionic) Status: New => 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/1836987 Title: update to 18.09.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1836987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815483] Re: [MIR] libhandy
desktop-package subscribed and package promotoed ** Changed in: libhandy (Ubuntu) Status: Incomplete => 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/1815483 Title: [MIR] libhandy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhandy/+bug/1815483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862734] Re: Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16
This bug was fixed in the package linux-firmware - 1.173.16 --- linux-firmware (1.173.16) bionic; urgency=medium * Failed to suspend once ever paired with BLE devices: PM: Device :00:14.0 failed to suspend async: error -16 (LP: #1862734) - linux-firmware: Update firmware file for Intel Bluetooth AX201 -- Seth Forshee Thu, 27 Feb 2020 13:24:55 -0600 ** Changed in: linux-firmware (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/1862734 Title: Failed to suspend once ever paired with BLE devices: PM: Device :00:14.0 failed to suspend async: error -16 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863669] Re: update to docker 19.03.6 and runc 1.0.0-rc10
This bug was fixed in the package runc - 1.0.0~rc10-0ubuntu1~18.04.1 --- runc (1.0.0~rc10-0ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic. (LP: #1863669, CVE-2019-19921) -- Michael Hudson-Doyle Wed, 19 Feb 2020 14:04:03 +1300 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863669 Title: update to docker 19.03.6 and runc 1.0.0-rc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1863669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862734] Update Released
The verification of the Stable Release Update for linux-firmware 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/1862734 Title: Failed to suspend once ever paired with BLE devices: PM: Device :00:14.0 failed to suspend async: error -16 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863669] Re: update to docker 19.03.6 and runc 1.0.0-rc10
This bug was fixed in the package docker.io - 19.03.6-0ubuntu1~19.10.1 --- docker.io (19.03.6-0ubuntu1~19.10.1) eoan; urgency=medium * Backport to eoan. (LP: #1863669) -- Michael Hudson-Doyle Wed, 19 Feb 2020 14:04:38 +1300 ** Changed in: docker.io (Ubuntu Eoan) Status: Fix Committed => Fix Released ** Changed in: runc (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/1863669 Title: update to docker 19.03.6 and runc 1.0.0-rc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1863669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863664] Re: can't add users to quassel
This bug was fixed in the package quassel - 1:0.12.4-3ubuntu1.18.04.1 --- quassel (1:0.12.4-3ubuntu1.18.04.1) bionic; urgency=medium * Cherry-pick fix introduced in Debian in revision 1:0.13.1-2 to fix apparmor profile (LP: #1863664) -- Gianfranco Costamagna Mon, 17 Feb 2020 19:06:19 +0100 ** Changed in: quassel (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/1863664 Title: can't add users to quassel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1863664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3
Would it be possible for you to do a kernel bisection? First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854363] Re: [upstream] ReferenceError: processLDAPValues is not defined
This should now be fixed, as bionic and eoan have thunderbird 68.4.1, while focal has 68.5.0. Feel free to re-open with a comment detailing the version you're running if this is still a problem. ** Changed in: thunderbird (Ubuntu Bionic) Status: Confirmed => Triaged ** Changed in: thunderbird (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: thunderbird (Ubuntu) Status: Confirmed => 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/1854363 Title: [upstream] ReferenceError: processLDAPValues is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1854363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866480] Re: focal/linux-raspi2: 5.4.0-1005.5 -proposed tracker
** Summary changed: - focal/linux-raspi2: -proposed tracker + focal/linux-raspi2: 5.4.0-1005.5 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866480 Title: focal/linux-raspi2: 5.4.0-1005.5 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866480] Re: focal/linux-raspi2: 5.4.0-1005.5 -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: 1866488 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Ready for Packaging - phase-changed: Sunday, 08. March 2020 03:06 UTC + phase: Packaging + phase-changed: Monday, 09. March 2020 10:06 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded trackers: focal/linux-raspi2/pi-kernel: bug 1866479 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/1866480 Title: focal/linux-raspi2: 5.4.0-1005.5 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866369] Re: [snap] 80.0.3987.132 require new apparmor rules
*** This bug is a duplicate of bug 1616650 *** https://bugs.launchpad.net/bugs/1616650 It appears that the snap was updated while chromium was running, which messed up with the profile directory (revision 1040 mentioned in the logs is for version 80.0.3987.122). This is a known problem (bug #1616650), so I'm marking as a duplicate. I strongly suggest you enable app refresh awareness¹ to avoid this in the future: snap set core experimental.refresh-app-awareness=true ¹ https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736 ** This bug has been marked a duplicate of bug 1616650 snap refresh while command is running may cause issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866369 Title: [snap] 80.0.3987.132 require new apparmor rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hello Hui, or anyone else affected, Accepted alsa-lib into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.1.9-0ubuntu1.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, what testing has been performed on the package 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. ** Tags removed: verification-failed verification-failed-eoan ** 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/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
Nothing really suspicious in there (the Gtk message about mapping a dialog without a transient parent can be safely ignored). Can you close chromium, execute the following command in a terminal, run it again and see whether that fixes the problem? rm -rf ~/snap/chromium/common/.cache -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858858] Re: aiol stressor not supported, but ran anyway
Verified eoan 0.10.07-1ubuntu4 is fixed. ** Tags removed: verification-needed-eoan ** Tags added: 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/1858858 Title: aiol stressor not supported, but ran anyway To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1858858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hello Hui, or anyone else affected, Accepted alsa-lib into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.1.3-5ubuntu0.4 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, what testing has been performed on the package 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. ** Tags removed: verification-failed-bionic ** 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/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
Hi Olivier, Emptying the snap cache fixed my issue. I'll definitely keep that in mind if I stumble upon any other issue with a snap software! Many thanks, Steven -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860041] Re: shiftfs: prevent lower dentries from going negative during unlink
** Tags removed: verification-needed-eoan ** Tags added: 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/1860041 Title: shiftfs: prevent lower dentries from going negative during unlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865480] Re: bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker
** Summary changed: - bionic/linux-oracle: 4.15.0-1035.38 -proposed tracker + bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865480 Title: bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865480] Re: bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Holding before Promote to Proposed - phase-changed: Thursday, 05. March 2020 06:51 UTC + phase: Packaging + phase-changed: Monday, 09. March 2020 10:21 UTC reason: - build-packages-ppa: Pending -- building in ppa lrm:depwait - main:failed meta:depwait signed:depwait + build-packages-ppa: Pending -- building in ppa lrm:missing + main:missing meta:depwait signed:missing + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: xenial/linux-oracle: bug 1865479 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/1865480 Title: bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866611] [NEW] OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
Public bug reported: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: openvpn sha1 ** Tags added: openvpn ** Tags added: sha1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804261] Re: Ceph OSD units requires reboot if they boot before vault (and if not unsealed with 150s)
What is the test case for verification of this bug as part of the SRU? Since this bug is called out as being fixed by the new upload, please include the basic SRU information such as Test Case and Regression Potential. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804261 Title: Ceph OSD units requires reboot if they boot before vault (and if not unsealed with 150s) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/1804261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855137] Re: characters sent to window upon workspace move
I would like to comment that this bug manifests itself in many different ways, depending on the program that happens to be in focus on the desktop. Many people probably use the mouse to change desktops (yikes!), but this problem may pop up in strange ways if it's not dealt with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855137 Title: characters sent to window upon workspace move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1855137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866047] Re: [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999)
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc5/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866047 Title: [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
Don't know if someone should mark as fix committed in this case, seeing as there are fixes out there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
Also works for me. In my case, I ran the binary on Ubuntu 18.04 because that's what my real hardware is using. If we can get this into Focal, that'd be great, but I wonder if we can backport into previous releases as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866612] [NEW] Wrong dependency javaproperties -> pyjavaproperties
Public bug reported: Due to a silly mistake by the Debian maintainer (*cough*) python3-azure- cli depends on python3-pyjavaproperties instead of python3-javaproperties. They are different and incompatible implementations. This has been fixed in Debian with the azure-cli 2.0.81+ds-3 upload and with the new source package javaproperties upload: https://tracker.debian.org/pkg/azure-cli https://tracker.debian.org/pkg/javaproperties Only a submodule of azure-cli uses this dependency, so general functionality is not affected - however that module cannot work. Please consider syncing javaproperties and azure-cli from Debian to Focal to fix this issue. azure-cli 2.0.81+ds-3 also gained autopkgtest support, and the build is now reproducible, which are very nice to have. ** Affects: azure-cli (Ubuntu) Importance: Undecided Status: New ** Tags: focal patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866612 Title: Wrong dependency javaproperties -> pyjavaproperties To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/azure-cli/+bug/1866612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853446] Re: linux-raspi2: set two flavours to armhf kernel and change the flavour name to raspi4 for arm64 kernel
** Changed in: linux-raspi2 (Ubuntu Focal) Status: Confirmed => Won't Fix ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853446 Title: linux-raspi2: set two flavours to armhf kernel and change the flavour name to raspi4 for arm64 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865247] Re: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker
** Summary changed: - bionic/linux-kvm: 4.15.0-1056.56 -proposed tracker + bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865247 Title: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
Thanks for the feedback Steven. I'm glad the problem is gone. I wish we'd gone to the bottom of it, if the issue is ever reported again I'll look into it further. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866613] [NEW] focal/linux-raspi2: Upstream raspberrypi patchset 2020-03-09
Public bug reported: Upstream raspberrypi patchset 2020-03-09 Ported from the following raspberrypi branch: rpi-5.4.y from https://github.com/raspberrypi/linux.git overlays: sc16ic750-i2c: Fix xtal parameter configs: Add KVM support to arm64 bcm2711_defconfig configs: Add CONFIG_EXT4_ENCRYPTION=y configs: Add CONFIG_HID_STEAM=m of: overlay: Correct symbol path fixups bcmrpi3_defconfig: align RC config with bcm2711_defconfig defconfigs: enable CONFIG_BPF_LIRC_MODE2 overlays: Add timeout_ms parameter to gpio-poweroff staging: vc04_services: Fix vcsm overflow bug when counting transactions ARM: dts: overlays: Create custom clocks in / Revert "ARM: dts: bcm283x: Restore simple-bus to /clocks" ARM: dts: bcm283x: Restore simple-bus to /clocks ASoC: pcm512x: Fix unbalanced regulator enable call in probe error path ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-raspi2-5.4 (Ubuntu) ** Also affects: linux-raspi2 (Ubuntu Focal) 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/1866613 Title: focal/linux-raspi2: Upstream raspberrypi patchset 2020-03-09 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1866613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865247] Re: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Kleber Sacilotto de Souza (kleber-souza) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865109 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Promote to Proposed - phase-changed: Monday, 02. March 2020 05:02 UTC + phase: Packaging + phase-changed: Monday, 09. March 2020 10:46 UTC reason: - build-packages-ppa: Pending -- building in ppa main:failed + prepare-package: Pending -- package not yet uploaded replaces: bug 1864737 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/1865247 Title: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865480] Re: bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Packaging - phase-changed: Monday, 09. March 2020 10:21 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 09. March 2020 10:51 UTC reason: - build-packages-ppa: Pending -- building in ppa lrm:missing - main:missing meta:depwait signed:missing - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + build-packages-ppa: Ongoing -- building in ppa main:building trackers: xenial/linux-oracle: bug 1865479 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/1865480 Title: bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Description changed: - Test failure in fallocate06 was composed by two issues, one is btrfs - fill_fs test issue addressed in bug 1866323. + == SRU Justification == + The fill_fs test for XFS in fallocate06 from ubuntu_ltp_syscalls will fail on X/B/D/E: + tst_test.c:1290: INFO: Testing on xfs + tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' + tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s + fallocate06.c:117: INFO: Copy-on-write is not supported + fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no + fallocate06.c:157: PASS: write() successful + fallocate06.c:201: PASS: Misaligned allocation works as expected + fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful + fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range + fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no + tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 + tst_fill_fs.c:59: INFO: write(): ENOSPC (28) + fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 8192) + fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful + fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range + + == Fix == + * e093c4be (xfs: Fix tail rounding in xfs_alloc_file_space()) + + This patch can be cherry-picked in D/E and needs some minor context + adjustmest on X/B. + + == Test == + Test kernels can be found here: + https://people.canonical.com/~phlin/kernel/lp-1865967-xfs-fallocate06/ + + All patched kernels are working as expected, this issue will no longer + exist on XFS: + tst_test.c:1290: INFO: Testing on xfs + tst_mkfs.c:90: INFO: Formatting /dev/loop5 with xfs opts='' extra opts='' + tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s + fallocate06.c:117: INFO: Copy-on-write is not supported + fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no + fallocate06.c:157: PASS: write() successful + fallocate06.c:201: PASS: Misaligned allocation works as expected + fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful + fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range + fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no + tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 + tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 + tst_fill_fs.c:59: INFO: write(): ENOSPC (28) + fallocate06.c:157: PASS: write() successful + fallocate06.c:201: PASS: Misaligned allocation works as expected + fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful + fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range + + == Regression Potential == + Low, this ensures all the blocks are properly allocated and it's only affecting the allocation on XFS. + + + == Original Bug Report == + Test failure in fallocate06 was composed by two issues, one is btrfs fill_fs test issue addressed in bug 1866323. Another is this one, this is the case 2 of xfs (fill_fs): tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1
[Bug 1864571] Proposed package upload rejected
An upload of ubuntu-dev-tools to bionic-proposed has been rejected from the upload queue for the following reason: "I think I need more clarification on this one before we can accept it (early reject). On the bug there is mention of it: this upload removes the python-ubuntutools package per the focal version. There were concerns of existing users using this package, but I see no attempts of making the situation better for those. What is the situation? Has it been assessed that there are no users of it? I also saw a proposal of re-adding the python2 support package with the backport, not to regress.". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864571 Title: SRU ubuntu-dev-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1864571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866612] Re: Wrong dependency javaproperties -> pyjavaproperties
** Tags added: focal ** Description changed: Due to a silly mistake by the Debian maintainer (*cough*) python3-azure- cli depends on python3-pyjavaproperties instead of python3-javaproperties. They are different and incompatible implementations. This has been fixed in Debian with the azure-cli 2.0.81+ds-3 upload and with the new source package javaproperties upload: https://tracker.debian.org/pkg/azure-cli https://tracker.debian.org/pkg/javaproperties Only a submodule of azure-cli uses this dependency, so general functionality is not affected - however that module cannot work. Please consider syncing javaproperties and azure-cli from Debian to Focal to fix this issue. - azure-cli 2.0.81+ds-3 also gained autopkgtest support, which is very - nice to have. + azure-cli 2.0.81+ds-3 also gained autopkgtest support, and the build is + now reproducible, which are very nice to have. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866612 Title: Wrong dependency javaproperties -> pyjavaproperties To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/azure-cli/+bug/1866612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
Hi Olivier, At your disposal to provide you with any additional information that might help you find the origin of the issue. It's a but strange that emptying the cache did the trick as I experienced the issue even after removing (with --purge flag) and re- installing the snap... If the issue arises again, I'll reopen this bug if that's ok with you. Thanks, Steven -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866012 Title: depmod ERROR during Setting up linux-modules-5.4.0-17-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802614] Re: [MIR] gnome-remote-desktop
@Jonathan > the security team appears to have approved it? the security team nacked the pipewire MIR, see bug #1802533. The Desktop team share the sentiment that it's a new project which hasn't had enough time to stabilize and be tested to be default/replace part of pulseaudio in this LTS @Aaron > My company is planning on replacing Ubuntu-based engineering laptops with desktops and then issuing windows laptops But you company isn't planning to stick the default/recommended session and opt in for wayland instead? Maybe that's a decision that your company should revisit... Also note that gnome-remote-desktop wouldn't help you much since you need RDP which isn't supported https://gitlab.gnome.org/jadahl/gnome-remote-desktop/issues/26 We recommend you stick to the default xorg session where rdp can be used without problem While having desktop sharing enabled in wayland would be nice adding/supporting pipewire at this point of the cycle would have an high cost for little benefit, our metrics telling us that less than 1% of the users opt in for a wayland session. We plan to look again at doing that post LTS though ** Bug watch added: gitlab.gnome.org/jadahl/gnome-remote-desktop/issues #26 https://gitlab.gnome.org/jadahl/gnome-remote-desktop/issues/26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802614 Title: [MIR] gnome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1802614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3
Currently I only have info for ubuntu kernel, the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. I have done some investigation, found the commit below, could you please help to check if this is one of the many differences between good and bad kernels that I mentioned? https://lore.kernel.org/patchwork/patch/1098499/ I will see if I can find a better machine to try your steps. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866487] Re: focal/linux-oracle: 5.4.0-1005.5 -proposed tracker
** Summary changed: - focal/linux-oracle: -proposed tracker + focal/linux-oracle: 5.4.0-1005.5 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati (p-pisati) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati (p-pisati) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866487 Title: focal/linux-oracle: 5.4.0-1005.5 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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/1865200 Title: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
Yes, please re-open this bug if the issue crops up again. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866487] Re: focal/linux-oracle: 5.4.0-1005.5 -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: 1866488 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Packaging - phase-changed: Sunday, 08. March 2020 03:08 UTC + phase: Packaging + phase-changed: Monday, 09. March 2020 11:21 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded 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/1866487 Title: focal/linux-oracle: 5.4.0-1005.5 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -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: 1865109 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Monday, 09. March 2020 09:06 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Stalled -- package copies requested to Proposed 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/1865200 Title: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -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: 1865109 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Monday, 09. March 2020 09:06 UTC reason: - promote-to-proposed: Stalled -- package copies requested to Proposed + build-packages-proposed: Pending -- building in Proposed + signed:queued + promote-to-proposed: Stalled -- packages copying to Proposed 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/1865200 Title: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866616] Re: 2nd display stopped working
The log shows "open /dev/dri/card0: No such file or directory" but it does exist: $ ls -l /dev/dri/card0 crw-rw+ 1 root render 226, 0 Mar 9 06:12 /dev/dri/card0 Unplugging the display from DVI-D-0 and plugging it back in does not result in showing up in xrandr output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866616 Title: 2nd display stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866616] [NEW] 2nd display stopped working
Public bug reported: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal regression reproducible ubuntu ** Description changed: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. - I've notices that Xorg.0.log shows fbdev rather than amdgpu in use (as - it had in the past). + I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd + monitor should be. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) -Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] + Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) + Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu
[Bug 1865247] Re: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** 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: 1865109 packages: main: linux-kvm meta: linux-meta-kvm - phase: Packaging - phase-changed: Monday, 09. March 2020 10:46 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 09. March 2020 11:27 UTC reason: - prepare-package: Pending -- package not yet uploaded + build-packages-ppa: Ongoing -- building in ppa main:building replaces: bug 1864737 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/1865247 Title: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
