[Bug 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2
Test kernel with commit 628859e8 reverted is at https://kernel.ubuntu.com/~ikepanhc/lp1852723/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852723 Title: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466046] Re: virtualbox doesnt run VMs since the vboxdrv module is not loaded automatically
This bug is still present in Ubuntu 19.10 and the fix "sudo modprobe vboxdrv" still works. See: https://askubuntu.com/q/1189888/156688 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466046 Title: virtualbox doesnt run VMs since the vboxdrv module is not loaded automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1466046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
$ sudo apt install linux-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853074] Re: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch
I think the git issues were a scheduled maintenance right? Anyway, while this is borderline between bug/feature I agree that it should have very low regression potential and OTOH will help people. So +1 on going forward with that. ** Description changed: [Impact] - * Despite libvirt having been compiled with libnss_libvirt_guest + * Despite libvirt having been compiled with libnss_libvirt_guest support, it only includes libnss_libvirt.so.2 shared library. With that, one that would like to use "libvirt_guest" as an entry in /etc/nsswitch.conf, to resolve hostnames (being the same as the virtual machine names) won't be able to. [Test Case] - * Create a virtual machine called "test" with hostname "untested" - * Make sure this virtual machine is attached to "default" network - * Make sure the "default" network offers DHCP addresses - * Edit /etc/nsswitch.conf: -... -hosts: files libvirt dns -... - * Confirm you're able to resolve "untested": ping untested - * Edit /etc/nsswitch.conf and change to: -... -hosts: files libvirt_guest dns -... - * You won't be able to resolve "test" (virtual machine name) + * Create a virtual machine called "test" with hostname "untested" + * Make sure this virtual machine is attached to "default" network + * Make sure the "default" network offers DHCP addresses + * Edit /etc/nsswitch.conf: + ... + hosts: files libvirt dns + ... + * Confirm you're able to resolve "untested": ping untested + * Edit /etc/nsswitch.conf and change to: + ... + hosts: files libvirt_guest dns + ... + * You won't be able to resolve "test" (virtual machine name) [Regression Potential] - * This change only includes a missing shared library in package libnss- + * This change only includes a missing shared library in package libnss- libvirt package. No code change: regressions could happen during package - building most likely. + building most likely. The lib is not used until you change nsswitch.conf [Other Info] Following the guidelines at: https://libvirt.org/nss.html I realized that we should be including libnss_libvirt.so.2 (as we are) and ALSO libnss_libvirt_guest.so.2 (not included) in the libnss-libvirt package. With that file missing, we can't solve libvirt machine names when changing nsswitch.conf "hosts" entry to "libvirt_guest" and we rely only in solving the guest hostname with "libvirt" only. ** Description changed: [Impact] - * Despite libvirt having been compiled with libnss_libvirt_guest - support, it only includes libnss_libvirt.so.2 shared library. With that, - one that would like to use "libvirt_guest" as an entry in - /etc/nsswitch.conf, to resolve hostnames (being the same as the virtual - machine names) won't be able to. + * Despite libvirt having been compiled with libnss_libvirt_guest support, +it only includes libnss_libvirt.so.2 shared library. With that, one +that would like to use "libvirt_guest" as an entry in +/etc/nsswitch.conf, to resolve hostnames (being the same as the virtual +machine names) won't be able to. [Test Case] - * Create a virtual machine called "test" with hostname "untested" - * Make sure this virtual machine is attached to "default" network + * Create a virtual machine called "test-guestname" with hostname +"test-hostname" +it is important that guestname and hostname differ. + * Make sure this virtual machine is attached to "default" network +(Default config) * Make sure the "default" network offers DHCP addresses +(Default config) * Edit /etc/nsswitch.conf: ... +# mode to resolve hostnames hosts: files libvirt dns ... - * Confirm you're able to resolve "untested": ping untested + * Confirm you're able to resolve "test-hostname": ping untested * Edit /etc/nsswitch.conf and change to: ... +# mode to resolve guestnames hosts: files libvirt_guest dns ... - * You won't be able to resolve "test" (virtual machine name) + * You won't be able to resolve "test-guestname" (virtual machine name) + * With the fix installed the latter will work as well [Regression Potential] * This change only includes a missing shared library in package libnss- - libvirt package. No code change: regressions could happen during package - building most likely. The lib is not used until you change nsswitch.conf +libvirt package. No code change: regressions could happen during +package building most likely. One might think "oh due to the install +now names will resolve differently", but they are not as the lib is not +used until you change nsswitch.conf as outlined above. [Other Info] Following the guidelines at: https://libvirt.org/nss.html I realized that we should be including libnss_libvirt.so.2 (as we are) and ALSO libnss_libvirt_guest.so.2 (not incl
[Bug 1853074] Re: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch
Slightly improved the SRU template, leaving the rest to you as you might have a local branch already ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853074 Title: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766775] Re: Notifications do not disappear
I have this bugin Ubuntu 19.10 Eaon. The suspend notification never goes away; also there is a " x " button but instead of closing the popup when you click on it the "settings" will open up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766775 Title: Notifications do not disappear To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798880] Re: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Remove the last physical PC card you installed. Or replace it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798880 Title: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1848797] Re: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found."
On Sun, Nov 17, 2019 at 12:26:48PM -, sacharja wrote: > Have an old VM 19.04 from May: after updating this system & then > upgrading to 19.10, it will reliably destroy grub. Let me know if you > need support to debug this, I'm reliably able to reproduce it. What is the output of 'debconf-show grub-pc' on this VM? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848797 Title: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848856] Re: zfs on root fails with grub syntax error with multidisks pools
I also tested the fix propossed by jpb in #21 and can confirm that it worked for me 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/1848856 Title: zfs on root fails with grub syntax error with multidisks pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830197] Re: e1000e driver - uploading slowed to a crawl.
You know what, now that you've pointed to it, while speedtest-cli produces the 4Mb upload rate, if i go to https://www.speedtest.net/, I get 1Gb symmetric. I'm on 16.04. Could it be a problem with speedtest- cli itself? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830197 Title: e1000e driver - uploading slowed to a crawl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848978] Re: CML: perf enabling for core
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Also affects: linux-oem-osp1 (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Disco) Status: New => Confirmed ** Changed in: linux-oem-osp1 (Ubuntu Eoan) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848978 Title: CML: perf enabling for core To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1848978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852978] Re: Asus USB-AC51 is not recognized by default on 4.15
Hi lotuspsychje, thanks for reporting this, it looks like Bionic is missing support for mt76x0 driver[1] and the mt76/mt76.h in mt76 driver. Considering the delta and the fact that user can still use this with the Bionic HWE kernel, I doubt the possibility to backport this into Bionic. I will let others to decide. Thanks [1] https://lwn.net/Articles/761344/ ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852978 Title: Asus USB-AC51 is not recognized by default on 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853102] [NEW] Update Vulkan loader in bionic to version 1.1.121
Public bug reported: [Impact] Currently bionic still uses an older version of the vulkan loader (version 1.1.70) with some fixes added on top. Since Vulkan api development is happening at a fast pace, the loader should be kept updated. The latest versions of the loader contain a lot of fixes and updates which are required to support latest version of Vulkan API. The latest loader, i.e., 1.1.121 or later should be made available with bionic. [Test case] Check all vulkan apps, so that they work as before. [Regression Potential] The vulkan loader is backwards compatible, so it should be an enhancement without regressing any functionality. ** Affects: vulkan (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/1853102 Title: Update Vulkan loader in bionic to version 1.1.121 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1853102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263505]
(In reply to neubland from comment #73) > a right click on hightlighted text "foobar.this" will recognize the > hightlighted text as not being a hyperlink That's bug 529085. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263505 Title: Wishlist: add "use input as a search term" to "address not found" page To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/263505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263505]
Does this issue include checking highlighted text against a cached Publix Suffix List? Meaning that a right click on hightlighted text "foobar.this" will recognize the hightlighted text as not being a hyperlink and therefore the context menu will not offer link-actions? I wonder because technically it might fall under the same scope of URL detection. If not I will create another bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263505 Title: Wishlist: add "use input as a search term" to "address not found" page To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/263505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263505]
(In reply to neubland from comment #73) > Does this issue include checking highlighted text against a cached Publix > Suffix List? Meaning that a right click on hightlighted text "foobar.this" > will recognize the hightlighted text as not being a hyperlink and therefore > the context menu will not offer link-actions? That would require a separate bug, this is only about the urlbar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263505 Title: Wishlist: add "use input as a search term" to "address not found" page To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/263505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848399] Re: update-grub fails if a pool fails to import
** Summary changed: - update-grub fails if zpools with unsupported feature_flags exist + update-grub fails if a pool fails to import -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848399 Title: update-grub fails if a pool fails to import To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852611] Re: update-grub fails because 10_linux_zfs puts a spare closed brace
*** This bug is a duplicate of bug 1848399 *** https://bugs.launchpad.net/bugs/1848399 ** This bug has been marked a duplicate of bug 1848399 update-grub fails if zpools with unsupported feature_flags exist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852611 Title: update-grub fails because 10_linux_zfs puts a spare closed brace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1852611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852233] Re: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 15. November 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress certification-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/1852233 Title: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770948] Re: Mouse cursor size is large and inconsistent on 4K displays in XFCE
Not sure. Maybe it is related somehow? If you explicitly set the cursor size does that temporarily resolve the issue for you? In my instance it does not change size when clicking. It remains large except it will change sizes mousing over certain applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770948 Title: Mouse cursor size is large and inconsistent on 4K displays in XFCE To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1770948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2
Good news. Patch 628859e8621cb landed in upstream kernel since 4.16 but we have no problem on 5.0 kernel. IIRC we don't have this issue on 4.18. Looks like this is a backport problem and to revert this patch might be the fast/best way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852723 Title: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852285] Re: xenial/linux-gcp: 4.15.0-1050.53 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1852283 xenial/linux-gcp/gke-kernel: bug 1852284 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/1852285 Title: xenial/linux-gcp: 4.15.0-1050.53 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager on aarch64 laptops
*** This bug is a duplicate of bug 1845289 *** https://bugs.launchpad.net/bugs/1845289 ** This bug has been marked a duplicate of bug 1845289 Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839317 Title: Grub fails to chainload the Windows Boot Manager on aarch64 laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852250] Re: bionic/linux-hwe: 5.0.0-37.40~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Thursday, 14. November 2019 23:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + 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 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/1852250 Title: bionic/linux-hwe: 5.0.0-37.40~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841646] Re: White text on white background for HTML e-mail
** Tags added: bionic regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841646 Title: White text on white background for HTML e-mail To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1841646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + 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: bionic/linux-hwe-edge: bug 1852231 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1852220 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 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/1852232 Title: eoan/linux: 5.3.0-24.26 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853094] [NEW] Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
Public bug reported: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day-to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Summary changed: - Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thubderbolt dock + Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock ** Description changed: - I have the WD19TB Thubderbolt dock connected to a Dell Latitude 7480 + I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day-to-day (#1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_AU.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day-to-day - (#1849405). + (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + 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: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 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/1852306 Title: xenial/linux: 4.4.0-170.199 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852289] Re: bionic/linux: 4.15.0-71.80 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + 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: bionic/linux-aws: bug 1852270 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1852274 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1852262 bionic/linux-snapdragon: bug 1852264 bionic/linux/pc-kernel: bug 1852259 bionic/linux/pc-lowlatency-kernel: bug 1852260 unknown/unknown: bug 1852288 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1852288 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/1852289 Title: bionic/linux: 4.15.0-71.80 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + 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: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 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/1852253 Title: disco/linux: 5.0.0-37.40 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2
Yes, reverting just that change seems to fix it for me on a Sabre board. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852723 Title: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
Oh nice, and I should install all the updates or just upgrade the grub? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + 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 trackers: bionic/linux-hwe-edge: bug 1852231 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1852220 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 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/1852232 Title: eoan/linux: 5.3.0-24.26 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + 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 trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 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/1852253 Title: disco/linux: 5.0.0-37.40 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852250] Re: bionic/linux-hwe: 5.0.0-37.40~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Thursday, 14. November 2019 23:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + 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/1852250 Title: bionic/linux-hwe: 5.0.0-37.40~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852233] Re: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 15. November 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED certification-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/1852233 Title: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852289] Re: bionic/linux: 4.15.0-71.80 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + 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 trackers: bionic/linux-aws: bug 1852270 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1852274 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1852262 bionic/linux-snapdragon: bug 1852264 bionic/linux/pc-kernel: bug 1852259 bionic/linux/pc-lowlatency-kernel: bug 1852260 unknown/unknown: bug 1852288 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1852288 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/1852289 Title: bionic/linux: 4.15.0-71.80 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852285] Re: xenial/linux-gcp: 4.15.0-1050.53 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1852283 xenial/linux-gcp/gke-kernel: bug 1852284 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/1852285 Title: xenial/linux-gcp: 4.15.0-1050.53 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + 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 trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 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/1852306 Title: xenial/linux: 4.4.0-170.199 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852978] Re: Asus USB-AC51 is not recognized by default on 4.15
Oh it's already in newer kernel, please use HWE kernel: https://wiki.ubuntu.com/Kernel/LTSEnablementStack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852978 Title: Asus USB-AC51 is not recognized by default on 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853061] Re: Connection to USB-C hub frequently drops when charging over it
Seems like it's a Thunderbolt Dock comes with Intel I210 ethernet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853061 Title: Connection to USB-C hub frequently drops when charging over it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2
My bisect landed on: 628859e8621cb arm64: capabilities: Change scope of VHE to Boot CPU feature I'm doing a build w/ that patch reverted to verify. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852723 Title: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852978] Re: Asus USB-AC51 is not recognized by default on 4.15
What's the output of `modinfo mt7601u`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852978 Title: Asus USB-AC51 is not recognized by default on 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850803]
*** This bug has been marked as a duplicate of bug 1503662 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850803 Title: Wrong wrap length when composing emails To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
So I should download this? https://www.ubuntuupdates.org/package/core/eoan/main/proposed/linux Then extract the .tar and follow these steps? http://www.berkes.ca/guides/linux_kernel.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853090] [NEW] failed to build DKMS fwts-efi-runtime-dkms/19.11.00 against v5.4-rc1 and on: numerous compile errors
Public bug reported:
1. Install ubuntu mainline kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc1/
2. sudo dkms install fwts-efi-runtime-dkms/19.11.00 -k 5.4.0-050400rc1-generic
make[1]: Entering directory '/usr/src/linux-headers-5.4.0-050400rc1-generic'
CC [M] /var/lib/dkms/fwts-efi-runtime-dkms/19.11.00/build/efi_runtime.o
In file included from :0:0:
./arch/x86/include/asm/segment.h: In function ‘vdso_read_cpunode’:
././include/linux/compiler_types.h:210:24: error: expected ‘(’ before ‘__inline’
#define asm_inline asm __inline
^
./arch/x86/include/asm/alternative.h:240:2: note: in expansion of macro
‘asm_inline’
asm_inline volatile (ALTERNATIVE(oldinstr, newinstr, feature) \
^~
./arch/x86/include/asm/segment.h:254:2: note: in expansion of macro
‘alternative_io’
alternative_io ("lsl %[seg],%[p]",
^~
In file included from ./arch/x86/include/asm/barrier.h:5:0,
from ./include/linux/compiler.h:256,
from ./include/linux/export.h:44,
from ./include/linux/linkage.h:7,
from ./include/linux/kernel.h:8,
from ./include/linux/list.h:9,
from ./include/linux/miscdevice.h:5,
from
/var/lib/dkms/fwts-efi-runtime-dkms/19.11.00/build/efi_runtime.c:23:
./arch/x86/include/asm/alternative.h:108:2: error: expected identifier or ‘(’
before string constant
...
Many errors dumped in the make.log.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: fwts 19.11.00-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-1016.18-oem-osp1 5.0.18
Uname: Linux 5.0.0-1016-oem-osp1 x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 18 23:59:52 2019
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X20
InstallationDate: Installed on 2019-11-14 (4 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20190418-12:10
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: fwts
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: fwts (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug bionic
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1853090/+attachment/5306408/+files/make.log
** Summary changed:
- failed to build against v5.4-rc1 and on: numerous compile errors
+ failed to build DKMS fwts-efi-runtime-dkms/19.11.00 against v5.4-rc1 and on:
numerous compile errors
** Description changed:
+ 1. Install ubuntu mainline kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc1/
+ 2. sudo dkms install fwts-efi-runtime-dkms/19.11.00 -k 5.4.0-050400rc1-generic
+
make[1]: Entering directory '/usr/src/linux-headers-5.4.0-050400rc1-generic'
- CC [M] /var/lib/dkms/fwts-efi-runtime-dkms/19.11.00/build/efi_runtime.o
+ CC [M] /var/lib/dkms/fwts-efi-runtime-dkms/19.11.00/build/efi_runtime.o
In file included from :0:0:
./arch/x86/include/asm/segment.h: In function ‘vdso_read_cpunode’:
././include/linux/compiler_types.h:210:24: error: expected ‘(’ before
‘__inline’
- #define asm_inline asm __inline
- ^
+ #define asm_inline asm __inline
+ ^
./arch/x86/include/asm/alternative.h:240:2: note: in expansion of macro
‘asm_inline’
- asm_inline volatile (ALTERNATIVE(oldinstr, newinstr, feature) \
- ^~
+ asm_inline volatile (ALTERNATIVE(oldinstr, newinstr, feature) \
+ ^~
./arch/x86/include/asm/segment.h:254:2: note: in expansion of macro
‘alternative_io’
- alternative_io ("lsl %[seg],%[p]",
- ^~
+ alternative_io ("lsl %[seg],%[p]",
+ ^~
In file included from ./arch/x86/include/asm/barrier.h:5:0,
- from ./include/linux/compiler.h:256,
- from ./include/linux/export.h:44,
- from ./include/linux/linkage.h:7,
- from ./include/linux/kernel.h:8,
- from ./include/linux/list.h:9,
- from ./include/linux/miscdevice.h:5,
- from
/var/lib/dkms/fwts-efi-runtime-dkms/19.11.00/build/efi_runtime.c:23:
+ from ./include/linux/compiler.h:256,
+ from ./include/linux/export.h:44,
+ from ./include/linux/linkage.h:7,
+ from ./include/linux/kernel.h:8,
+ from ./include/linux/list.h:9,
+ from ./include/linux/miscdevice.h:5,
+ from
/var/lib/dkms/fwts-efi-runtime-dkms/19.11.00/build/efi_runtime.c:23:
./arch/x86/include/asm/alternative.h:108:2: error: expected identifier or ‘(’
before string constant
...
[Bug 1853050] Re: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc8/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853050 Title: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852978] Re: Asus USB-AC51 is not recognized by default on 4.15
** Also affects: linux (Ubuntu Bionic) 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/1852978 Title: Asus USB-AC51 is not recognized by default on 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
Can you please test 5.3.0-24 from eoan-proposed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451216] Re: No notification after `sleep 30`
[Expired for undistract-me (Ubuntu) because there has been no activity for 60 days.] ** Changed in: undistract-me (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451216 Title: No notification after `sleep 30` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/undistract-me/+bug/1451216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1193787] Re: gpm mouse service doesn't work well in byobu
[Expired for byobu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: byobu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1193787 Title: gpm mouse service doesn't work well in byobu To manage notifications about this bug go to: https://bugs.launchpad.net/byobu/+bug/1193787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843998] Re: package dovecot-core 1:2.2.22-1ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for dovecot (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dovecot (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843998 Title: package dovecot-core 1:2.2.22-1ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1843998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841969] Re: chromium-browser crashes with ThreadPoolSingl trap bringing back to login screen
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841969 Title: chromium-browser crashes with ThreadPoolSingl trap bringing back to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1841969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813679] Re: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04
I did a bisect as asked in the upstream issue I reported at https://github.com/vim/vim/issues/5237 and I think that https://github.com/vim/vim/commit/cd142e3369db163a511dbe9907bcd138829c is the offending commit. ** Summary changed: - vim-gtk can no longer save to GVFS SFTP mounts in 18.04 + vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04 ** Bug watch added: github.com/vim/vim/issues #5237 https://github.com/vim/vim/issues/5237 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
** Description changed: After upgrading to 19.10 and rebooting. My machine goes into a frozen black screen. The default kernel after the update (5.3.0-23-generic) does not succeed in booting. If I select the older kernel, 5.0.0-36-generic, grub does go through and succeeds booting up. - System is a Dell XPS 15 9560 with Ubuntu Dual Boot. GRUB version + System is a Dell XPS 15 9550 with Ubuntu Dual Boot. GRUB version 2.04-1ubuntu12. The Windows partition does work properly, and I am able to boot into it. Please advice on how to proceed with a fix, or if an update pushed to grub will fix this issue. Thanks. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: pipemon2417 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: pipemon2417 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c26ef9c3-b999-4441-b750-cf80d00fc68e InstallationDate: Installed on 2017-11-02 (746 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen - Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications - Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen + Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications + Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic root=UUID=6b1a4315-6bdf-471f-90b5-6fb32c3bfc2b ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 RelatedPackageVersions: - linux-restricted-modules-5.0.0-36-generic N/A - linux-backports-modules-5.0.0-36-generic N/A - linux-firmware1.183.2 + linux-restricted-modules-5.0.0-36-generic N/A + linux-backports-modules-5.0.0-36-generic N/A + linux-firmware1.183.2 Tags: eoan Uname: Linux 5.0.0-36-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-18 (0 days ago) UserGroups: adm audio cdrom dialout dip kvm lpadmin plugdev pulse sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd07/30/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735355] Re: heartbeat: port to Python3
** Changed in: heartbeat (Debian) 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/1735355 Title: heartbeat: port to Python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heartbeat/+bug/1735355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2
Thanks Dann, It's very close. The root cause is somewhere between these commits and e988af01 is just few commits below. 5d0f174e40a6 ykau...@suse.de 2019-11-12 19:04:49 +0100 arm64: enable generic CPU vulnerabilites support f94f9d3a3e8b jeremy.lin...@arm.com 2019-11-12 19:04:49 +0100 arm64: add sysfs vulnerability show for meltdown c288f6b5788d ykau...@suse.de 2019-11-12 19:04:48 +0100 arm64: Add sysfs vulnerability show for spectre-v1 f2485ae5fd84 mark.rutl...@arm.com 2019-11-12 19:04:48 +0100 arm64: fix SSBS sanitization 1931a913df7e will.dea...@arm.com 2019-11-12 19:04:48 +0100 KVM: arm64: Set SCTLR_EL2.DSSBS if SSBD is forcefully disabled and !vhe fd872fd82e12 will.dea...@arm.com 2019-11-12 19:04:48 +0100 arm64: ssbd: Add support for PSTATE.SSBS rather than trapping to EL3 2a3135c3033c will.dea...@arm.com 2019-11-12 19:04:48 +0100 arm64: cpufeature: Detect SSBS and advertise to userspace 78dc3acb34fa marc.zyng...@arm.com 2019-11-12 19:04:48 +0100 arm64: Get rid of __smccc_workaround_1_hvc_* 5c43fb65359d mark.rutl...@arm.com 2019-11-12 19:04:48 +0100 arm64: don't zero DIT on signal return c6c07232325a shank...@codeaurora.org 2019-11-12 19:04:48 +0100 arm64: KVM: Use SMCCC_ARCH_WORKAROUND_1 for Falkor BP hardening 274adba3ccf6 suzuki.poul...@arm.com 2019-11-12 19:04:47 +0100 arm64: capabilities: Add support for checks based on a list of MIDRs f34e57c35b72 suzuki.poul...@arm.com 2019-11-12 19:04:47 +0100 arm64: Add MIDR encoding for Arm Cortex-A55 and Cortex-A35 8d811d39465c suzuki.poul...@arm.com 2019-11-12 19:04:47 +0100 arm64: Add helpers for checking CPU MIDR against a range b2eddaf65384 suzuki.poul...@arm.com 2019-11-12 19:04:47 +0100 arm64: capabilities: Clean up midr range helpers 628859e8621c suzuki.poul...@arm.com 2019-11-12 19:04:47 +0100 arm64: capabilities: Change scope of VHE to Boot CPU feature 3bf4ffd98cc4 suzuki.poul...@arm.com 2019-11-12 19:04:47 +0100 arm64: capabilities: Add support for features enabled early -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852723 Title: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851858] Re: adds ESM to sources.list.d unconditionally, despite it being x86-only
** Changed in: ubuntu-advantage-script 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/1851858 Title: adds ESM to sources.list.d unconditionally, despite it being x86-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1851858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848522] Autopkgtest regression report (mesa/19.2.1-1ubuntu1~18.04.1)
All autopkgtests for the newly accepted mesa (19.2.1-1ubuntu1~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: firefox/70.0.1+build1-0ubuntu0.18.04.1 (armhf) pymol/1.8.4.0+dfsg-1build1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1848522 Title: Backport packages for 18.04.4 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852966] Re: pivot_root01 from ubuntu_ltp_syscalls failed on D-Oracle-5.0
More tests: This test can pass on the same oracle instance by reverting commit ae52b6f4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852966 Title: pivot_root01 from ubuntu_ltp_syscalls failed on D-Oracle-5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1852966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853050] Re: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)
Do you have any issues with Bluetooth? I am facing frequent disconnections with Bluetooth module: https://bugs.launchpad.net/linux/+bug/1850502 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853050 Title: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813679] Re: vim-gtk can no longer save to GVFS SFTP mounts in 18.04
Sorry, I misremembered my results from yesterday. I just checked again. The permissions are in fact different: the Nautilus-created files are 644 (because my "New Text Document.txt" template in ~/Templates is 644), while files created with e.g. touch are 664. Since both allow me, the owning user, to write the file, vim still shouldn't have problems, but it does seem like that is the underlying cause, rather than Nautilus having been used to create the file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853082] Re: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853082 Title: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1853082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853082] [NEW] package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127
Public bug reported: the package could not update ProblemType: Package DistroRelease: Ubuntu 19.10 Package: mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Nov 18 21:54:26 2019 DuplicateSignature: package:mysql-server-8.0:8.0.18-0ubuntu0.19.10.1 Installing new version of config file /etc/mysql/mysql.conf.d/mysqld.cnf ... /var/lib/dpkg/info/mysql-server-8.0.postinst: line 191: /usr/share/mysql-common/configure-symlinks: No such file or directory dpkg: error processing package mysql-server-8.0 (--configure): installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2019-03-15 (248 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['undo_001', 'binlog.46', 'server-cert.pem', 'public_key.pem', 'ib_logfile0', 'binlog.49', 'ca.pem', 'binlog.47', '#innodb_temp', 'binlog.45', 'proj1', 'client-cert.pem', 'binlog.54', 'ca-key.pem', 'sakila', 'world', 'private_key.pem', 'ib_logfile1', 'tutorial', 'ib_buffer_pool', 'air_alliance', 'ibdata1', 'sys', 'mysql', 'client-key.pem', 'mysql.ibd', 'binlog.53', 'binlog.56', 'binlog.48', 'binlog.52', 'server-key.pem', 'mysql_upgrade_info', 'binlog.55', 'auto.cnf', 'performance_schema', 'binlog.50', 'socad', 'binlog.index', 'binlog.51', 'menagerie', 'undo_002'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=03d61b8e-2a61-4648-b0b8-cca18f023218 ro quiet splash nomodeset vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853082 Title: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1853082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852070] Re: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0]
** Also affects: oem-priority 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/1852070 Title: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1852070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812352] Re: Handle the skip return code in kernel_selftests on Bionic
Verified on Bionic. Works as expected. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812352 Title: Handle the skip return code in kernel_selftests on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791425]
The GCC 7 branch is being closed, re-targeting to GCC 8.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791425 Title: Compiler error: constexpr with bitfields. To manage notifications about this bug go to: https://bugs.launchpad.net/gcc-defaults/+bug/1791425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306378/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306374/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306379/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306377/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306381/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306375/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306370/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306382/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/linux/+question/686001 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306372/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306376/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306380/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
apport information ** Tags added: apport-collected eoan ** Description changed: After upgrading to 19.10 and rebooting. My machine goes into a frozen black screen. The default kernel after the update (5.3.0-23-generic) does not succeed in booting. If I select the older kernel, 5.0.0-36-generic, grub does go through and succeeds booting up. System is a Dell XPS 15 9560 with Ubuntu Dual Boot. GRUB version 2.04-1ubuntu12. The Windows partition does work properly, and I am able to boot into it. Please advice on how to proceed with a fix, or if an update pushed to grub will fix this issue. Thanks. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: pipemon2417 F pulseaudio + CurrentDesktop: KDE + DistroRelease: Ubuntu 19.10 + HibernationDevice: RESUME=UUID=c26ef9c3-b999-4441-b750-cf80d00fc68e + InstallationDate: Installed on 2017-11-02 (746 days ago) + InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen + Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications + Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. XPS 15 9550 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic root=UUID=6b1a4315-6bdf-471f-90b5-6fb32c3bfc2b ro quiet splash + ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-36-generic N/A + linux-backports-modules-5.0.0-36-generic N/A + linux-firmware1.183.2 + Tags: eoan + Uname: Linux 5.0.0-36-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-11-18 (0 days ago) + UserGroups: adm audio cdrom dialout dip kvm lpadmin plugdev pulse sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 07/30/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.11.2 + dmi.board.name: 0N7TVV + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd07/30/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 15 9550 + dmi.product.sku: 06E4 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306369/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306373/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1853075/+attachment/5306371/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852070] Re: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0]
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852070 Title: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1852070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1853075 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Note: If you can't boot the latest kernel, please NOTE it & run `apport- collect 1853075` using an older kernel (the detail won't be as pertinent, but it'll still have detail). This bug report can be converted to a question (which is aimed at support, bug reports are aimed and finding problems and fixing so subsequent users won't stumble with the same issue). You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] Re: 19.10 Boots into a black screen
** Description changed: After upgrading to 19.10 and rebooting. My machine goes into a frozen black screen. The default kernel after the update (5.3.0-23-generic) does not succeed in booting. If I select the older kernel, 5.0.0-36-generic, grub does go through and succeeds booting up. - System is a Dell XPS 15 9560 with Ubuntu Dual Boot. The Windows - partition does work properly, and I am able to boot into it. Please - advice on how to proceed with a fix, or if an update pushed to grub will - fix this issue. - + System is a Dell XPS 15 9560 with Ubuntu Dual Boot. GRUB version + 2.04-1ubuntu12. The Windows partition does work properly, and I am able + to boot into it. Please advice on how to proceed with a fix, or if an + update pushed to grub will fix this issue. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853074] Re: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch
Ill send the MRs tomorrow as it looks like launchpad git repos are having some issues currently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853074 Title: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853075] [NEW] 19.10 Boots into a black screen
Public bug reported: After upgrading to 19.10 and rebooting. My machine goes into a frozen black screen. The default kernel after the update (5.3.0-23-generic) does not succeed in booting. If I select the older kernel, 5.0.0-36-generic, grub does go through and succeeds booting up. System is a Dell XPS 15 9560 with Ubuntu Dual Boot. GRUB version 2.04-1ubuntu12. The Windows partition does work properly, and I am able to boot into it. Please advice on how to proceed with a fix, or if an update pushed to grub will fix this issue. Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: boot grub kernel-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849563] Re: Unable to passthrough GPUs to guest
Discussion thread on edk2 list: https://edk2.groups.io/g/discuss/topic/ovmf_resource_assignment/59340711?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,59340711 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849563 Title: Unable to passthrough GPUs to guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1849563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1813679] Re: vim-gtk can no longer save to GVFS SFTP mounts in 18.04
The permissions and ownership are the same. It seems to persist across ejecting and remounting the SSH mount. I can see if it persists across a reboot or magically spreads from one SSH mount to a different mount (via a different hostname/ip for the same machine), but I suspect it won't. November 18, 2019 12:37 PM, "Sebastien Bacher" wrote: > Thank you for your bug report. Does it only happen directly after > creating the file or is it still an issue for those files after e.G a > reboot? > > Could you see if there is anything different in permission/ownership > between the files created by nautilus and from the commandline? > > ** Changed in: nautilus (Ubuntu) > Importance: Undecided => Low > > ** Changed in: nautilus (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1813679 > > Title: > vim-gtk can no longer save to GVFS SFTP mounts in 18.04 > > Status in gvfs package in Ubuntu: > New > Status in nautilus package in Ubuntu: > Incomplete > Status in vim package in Ubuntu: > New > > Bug description: > In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH > mounts (by going to `ssh://wherever` in the address bar in the file > browser and double-clicking on the file), edit them, and save them. > > In Ubuntu 18.04, when I install `vim-gtk` and try to do the same > thing, I can open the files just fine, but when I try to save them I > get a message that Vim "Can't open file for writing". > > If I check out the Vim source tree and build and install vim > v7.4.1689, which is what Xenial is shipping now, and use *that* gvim > on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from > gedit. > > Something is wrong with the gvim shipping with 18.04. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: vim-gtk (not installed) > ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 > Uname: Linux 4.15.0-44-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Mon Jan 28 15:55:56 2019 > ProcEnviron: > TERM=xterm-256color > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: vim > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853074] Re: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch
** Description changed: + [Impact] + + * Despite libvirt having been compiled with libnss_libvirt_guest + support, it only includes libnss_libvirt.so.2 shared library. With that, + one that would like to use "libvirt_guest" as an entry in + /etc/nsswitch.conf, to resolve hostnames (being the same as the virtual + machine names) won't be able to. + + [Test Case] + + * Create a virtual machine called "test" with hostname "untested" + * Make sure this virtual machine is attached to "default" network + * Make sure the "default" network offers DHCP addresses + * Edit /etc/nsswitch.conf: +... +hosts: files libvirt dns +... + * Confirm you're able to resolve "untested": ping untested + * Edit /etc/nsswitch.conf and change to: +... +hosts: files libvirt_guest dns +... + * You won't be able to resolve "test" (virtual machine name) + + [Regression Potential] + + * This change only includes a missing shared library in package libnss- + libvirt package. No code change: regressions could happen during package + building most likely. + + [Other Info] + Following the guidelines at: https://libvirt.org/nss.html I realized that we should be including libnss_libvirt.so.2 (as we are) and ALSO libnss_libvirt_guest.so.2 (not included) in the libnss-libvirt package. With that file missing, we can't solve libvirt machine names when changing nsswitch.conf "hosts" entry to "libvirt_guest" and we rely only in solving the guest hostname with "libvirt" only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853074 Title: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853074] [NEW] libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch
Public bug reported: Following the guidelines at: https://libvirt.org/nss.html I realized that we should be including libnss_libvirt.so.2 (as we are) and ALSO libnss_libvirt_guest.so.2 (not included) in the libnss-libvirt package. With that file missing, we can't solve libvirt machine names when changing nsswitch.conf "hosts" entry to "libvirt_guest" and we rely only in solving the guest hostname with "libvirt" only. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libvirt (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Affects: libvirt (Ubuntu Disco) Importance: Medium Status: Confirmed ** Affects: libvirt (Ubuntu Eoan) Importance: Undecided Status: Fix Released ** Affects: libvirt (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Also affects: libvirt (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Disco) Status: New => Confirmed ** Changed in: libvirt (Ubuntu Disco) Importance: Undecided => Medium ** Also affects: libvirt (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Bionic) Status: New => Confirmed ** Changed in: libvirt (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libvirt (Ubuntu Bionic) Importance: High => Medium ** Also affects: libvirt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Eoan) Status: New => Fix Released ** Changed in: libvirt (Ubuntu Focal) 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/1853074 Title: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853074] Re: libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch
It was fixed in:
* [447dd58] libnss-libvirt: Install libnss_libvirt-guest as well
(Closes: #910288)
upstream:
libvirt (5.2.0-2) experimental; urgency=medium
[ Guido Günther ]
* [1ec90c0] d/compat: Switch to debhelper level 12
* [fb6dd18] d/rules: s/no-restart-on-upgrade/no-stop-on-upgrade/
* [3764b71] d/rules: --prallel not needed anymore
* [1d92095] d/control: Add ${misc:Pre-Depends} for
libvirt-daemon-system. This makes sure we pull in recent enough
init-system-helpers
* [02a155b] d/rules: Switch to dh_installsystemd
dh_systemd_start is no longer used.
* [bcad111] d/control: Fix typo
* [8609192] d/control: Drop Debian revision on iptables build-dep. Any
version greater than 1.8.1 will do.
* [447dd58] libnss-libvirt: Install libnss_libvirt-guest as well
(Closes: #910288)
* [4fb7d11] d/control: Build-depend on libglusterfs-dev.
Since this is a recent addition we can drop the versioned dependency.
(Closes: #919663)
* [7b4ffeb] d/rules: Newer debhelper puts the libs into multi arch dirs.
There's no need to move them manually anymore.
[ Andrea Bolognani ]
* [dd9cdaa] Use HTTPS for all URLs.
This gets rid of the debian-watch-uses-insecure-uri informational Lintian
tag, and then some.
* [faaec12] Minimize upstream's signing key.
This gets rid of the public-upstream-key-not-minimal informational Lintian
tag.
* [8a0e6f1] Remove Priority field from binary packages.
This gets rid of the binary-control-field-duplicates-source informational
Lintian tag.
[ Christian Ehrhardt ]
* [08f3a23] d/libvirt-clients.manpages: add virkeycode and virkeyname man
pages.
* [0f359de] d/rules: mv logrotate files to silence dh_missing
* [f36ca33] dh_missing: ignore warning on libtool .la file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853074
Title:
libnss-libvirt does not include libnss_libvirt_guest.so for nsswitch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853074/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Ok after I removed the patches and the normal Kernel-Update to 5.3.11 happend, I'm experiencing the same higher power consumption that happend during the test before. It could be related to something else not the patches. But I'm unable to find out atm. where it comes from :( The pc is not going below 10W with 5.3.11 on 5.3.8 it drops to 7-8W. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852854] Re: Update of zfs-linux fails
** Changed in: zfs-linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852854 Title: Update of zfs-linux fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852616] Re: r8168-dkms 8.047.04-1 fails to build with 5.4 kernel
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852616 Title: r8168-dkms 8.047.04-1 fails to build with 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1852616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852338] Re: Eoan update: 5.3.11 upstream stable release
Please note that the following SAUCE patches were reverted: * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: kvm: x86: mmu: Recovery of shattered NX large pages" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: kvm: Add helper function for creating VM worker threads" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: kvm: mmu: ITLB_MULTIHIT mitigation" * UBUNTU: SAUCE: Revert "kvm: x86, powerpc: do not allow clearing largepages debugfs entry" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: cpu/speculation: Uninline and export CPU mitigations helpers" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: x86: Add ITLB_MULTIHIT bug infrastructure" * UBUNTU: SAUCE: Revert "x86/tsx: Add config options to set tsx=on|off|auto" * UBUNTU: SAUCE: Revert "x86/speculation/taa: Add documentation for TSX Async Abort" * UBUNTU: SAUCE: Revert "x86/tsx: Add "auto" option to the tsx= cmdline parameter" * UBUNTU: SAUCE: Revert "kvm/x86: Export MDS_NO=0 to guests when TSX is enabled" * UBUNTU: SAUCE: Revert "x86/speculation/taa: Add sysfs reporting for TSX Async Abort" * UBUNTU: SAUCE: Revert "x86/speculation/taa: Add mitigation for TSX Async Abort" * UBUNTU: SAUCE: Revert "x86/cpu: Add a "tsx=" cmdline option with TSX disabled by default" * UBUNTU: SAUCE: Revert "x86/cpu: Add a helper function x86_read_arch_cap_msr()" * UBUNTU: SAUCE: Revert "x86/msr: Add the IA32_TSX_CTRL MSR" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915/cmdparser: Fix jump whitelist clearing" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915/gen8+: Add RC6 CTX corruption WA" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915: Lower RM timeout to avoid DSI hard hangs" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915/cmdparser: Ignore Length operands during command matching" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915/cmdparser: Add support for backward jumps" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915/cmdparser: Use explicit goto for error paths" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915: Add gen9 BCS cmdparsing" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915: Allow parsing of unsized batches" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915: Support ro ppgtt mapped cmdparser shadow buffers" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915: Add support for mandatory cmdparsing" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915: Remove Master tables from cmdparser" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915: Disable Secure Batches for gen6+" * UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: drm/i915: Rename gen7 cmdparser tables" In favor of their upstream stable versions: * drm/i915: Rename gen7 cmdparser tables * drm/i915: Disable Secure Batches for gen6+ * drm/i915: Remove Master tables from cmdparser * drm/i915: Add support for mandatory cmdparsing * drm/i915: Support ro ppgtt mapped cmdparser shadow buffers * drm/i915: Allow parsing of unsized batches * drm/i915: Add gen9 BCS cmdparsing * drm/i915/cmdparser: Use explicit goto for error paths * drm/i915/cmdparser: Add support for backward jumps * drm/i915/cmdparser: Ignore Length operands during command matching * drm/i915: Lower RM timeout to avoid DSI hard hangs * drm/i915/gen8+: Add RC6 CTX corruption WA * drm/i915/cmdparser: Fix jump whitelist clearing * x86/msr: Add the IA32_TSX_CTRL MSR * x86/cpu: Add a helper function x86_read_arch_cap_msr() * x86/cpu: Add a "tsx=" cmdline option with TSX disabled by default * x86/speculation/taa: Add mitigation for TSX Async Abort * x86/speculation/taa: Add sysfs reporting for TSX Async Abort * kvm/x86: Export MDS_NO=0 to guests when TSX is enabled * x86/tsx: Add "auto" option to the tsx= cmdline parameter * x86/speculation/taa: Add documentation for TSX Async Abort * x86/tsx: Add config options to set tsx=on|off|auto * x86/speculation/taa: Fix printing of TAA_MSG_SMT on IBRS_ALL CPUs * x86/bugs: Add ITLB_MULTIHIT bug infrastructure * x86/cpu: Add Tremont to the cpu vulnerability whitelist * cpu/speculation: Uninline and export CPU mitigations helpers * Documentation: Add ITLB_MULTIHIT documentation * kvm: x86, powerpc: do not allow clearing largepages debugfs entry * kvm: mmu: ITLB_MULTIHIT mitigation * kvm: Add helper function for creating VM worker threads * kvm: x86: mmu: Recovery of shattered NX large pages ** Description changed: - - SRU Justification - - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: - -5.3.11 upstream stable release -from git://git.kernel.org/ + SRU Justification + + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably
[Bug 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
** Changed in: glib Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1852844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852288] Re: xenial/linux-hwe: 4.15.0-71.80~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Holding before Promote to Proposed - phase-changed: Monday, 18. November 2019 15:51 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 18. November 2019 23:46 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait + promote-to-proposed: Pending -- ready for review trackers: xenial/linux-deeplens: bug 1852287 xenial/linux-hwe-edge: bug 1852286 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/1852288 Title: xenial/linux-hwe: 4.15.0-71.80~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852251] Re: bionic/linux-oem-osp1: 5.0.0-1029.33 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: lrm: linux-restricted-modules-oem-osp1 main: linux-oem-osp1 meta: linux-meta-oem-osp1 signed: linux-signed-oem-osp1 - phase: Holding before Promote to Proposed - phase-changed: Monday, 18. November 2019 21:11 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 18. November 2019 23:46 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait + promote-to-proposed: Pending -- ready for review 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/1852251 Title: bionic/linux-oem-osp1: 5.0.0-1029.33 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853067] [NEW] Disco update: upstream stable patchset 2019-11-18
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-11-18 Ported from the following upstream stable releases: v4.19.82, v5.3.9 from git://git.kernel.org/ dm snapshot: introduce account_start_copy() and account_end_copy() dm snapshot: rework COW throttling to fix deadlock Btrfs: fix inode cache block reserve leak on failure to allocate data space btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents() f2fs: flush quota blocks after turnning it off drm/msm/dpu: handle failures while initializing displays bcache: fix input overflow to writeback_rate_minimum ath10k: assign 'n_cipher_suites = 11' for WCN3990 to enable WPA3 staging: mt7621-pinctrl: use pinconf-generic for 'dt_node_to_map' and 'dt_free_map' HID: Add ASUS T100CHI keyboard dock battery quirks HID: steam: fix boot loop with bluetooth firmware HID: steam: fix deadlock with input devices. usb: dwc3: gadget: early giveback if End Transfer already completed usb: dwc3: gadget: clear DWC3_EP_TRANSFER_STARTED on cmd complete ALSA: usb-audio: Cleanup DSD whitelist usb: handle warm-reset port requests on hub resume rtc: pcf8523: set xtal load capacitance from DT arm64: Add MIDR encoding for HiSilicon Taishan CPUs arm64: kpti: Whitelist HiSilicon Taishan v110 CPUs mlxsw: spectrum: Set LAG port collector only when active scsi: lpfc: Correct localport timeout duration error CIFS: Respect SMB2 hdr preamble size in read responses cifs: add credits from unmatched responses/messages ALSA: hda/realtek - Apply ALC294 hp init also for S4 resume media: vimc: Remove unused but set variables ext4: disallow files with EXT4_JOURNAL_DATA_FL from EXT4_IOC_SWAP_BOOT net: dsa: mv88e6xxx: Release lock while requesting IRQ PCI/PME: Fix possible use-after-free on remove drm/amd/display: fix odm combine pipe reset power: supply: max14656: fix potential use-after-free iio: adc: meson_saradc: Fix memory allocation order iio: fix center temperature of bmc150-accel-core libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature perf tests: Avoid raising SEGV using an obvious NULL dereference perf map: Fix overlapped map handling perf script brstackinsn: Fix recovery from LBR/binary mismatch perf jevents: Fix period for Intel fixed counters perf tools: Propagate get_cpuid() error perf annotate: Propagate perf_env__arch() error perf annotate: Fix the signedness of failure returns perf annotate: Propagate the symbol__annotate() error return perf annotate: Return appropriate error code for allocation failures staging: rtl8188eu: fix null dereference when kzalloc fails RDMA/hfi1: Prevent memory leak in sdma_init RDMA/iwcm: Fix a lock inversion issue HID: hyperv: Use in-place iterator API in the channel callback nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419 tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' tty: n_hdlc: fix build on SPARC gpio: max77620: Use correct unit for debounce times fs: cifs: mute -Wunused-const-variable message serial: mctrl_gpio: Check for NULL pointer efi/cper: Fix endianness of PCIe class code efi/x86: Do not clean dummy variable in kexec path MIPS: include: Mark __cmpxchg as __always_inline x86/xen: Return from panic notifier ocfs2: clear zero in unaligned direct IO fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry() fs: ocfs2: fix a possible null-pointer dereference in ocfs2_write_end_nolock() fs: ocfs2: fix a possible null-pointer dereference in ocfs2_info_scan_inode_alloc() arm64: armv8_deprecated: Checking return value for memory allocation sched/vtime: Fix guest/system mis-accounting on task switch perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp drm/amdgpu: fix memory leak iio: imu: adis16400: release allocated memory on failure MIPS: include: Mark __xchg as __always_inline MIPS: fw: sni: Fix out of bounds init of o32 stack virt: vbox: fix memory leak in hgcm_call_preprocess_linaddr nbd: fix possible sysfs duplicate warning NFSv4: Fix leak of clp->cl_acceptor string s390/uaccess: avoid (false positive) compiler warnings tracing: Initialize iter->seq after zeroing in tracing_read_pipe() ARM: 8914/1: NOMMU: Fix exc_ret for XIP ALSA: hda/realtek: Reduce the Headphone static noise on XPS 9350/9360 nbd: verify socket is supported during setup USB: legousbtower: fix a signedness bug in tower_probe() thunderbolt: Use 32-bit writes when writing ring producer/consumer fuse: flush d
