[Bug 1848980] Re: system hangs on suspend
Please attach `journalctl -b -1 -k` from the next boot of system hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848980 Title: system hangs on suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849041] Re: xenial/linux-aws: 4.4.0-1097.108 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849051 packages: main: linux-aws meta: linux-meta-aws - phase: Packaging - phase-changed: Monday, 21. October 2019 21:50 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 22. October 2019 05:41 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: xenial/linux-aws/aws-kernel: bug 1849040 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/1849041 Title: xenial/linux-aws: 4.4.0-1097.108 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849136] Re: errors at boot and long boot time
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849136 Title: errors at boot and long boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Hi Rafael, thanks for giving it try. We knew it might be complex when we first saw the changes. And I consider it wise to - at some point - step back and realize this won't be SRUable. I'll summarize what we know about the libvirt portion of this: ## SRUability ## The changes are rather complex, and will most likely not be SRUable. Even if prepared for an upload they are massive and with a huge risk of regressing other use cases which we'd generally want to avoid. I haven't done/tried the porting myself, but your doc reads fine and it grows and grows to become borderline to considering a major version bump which isn't an option here. ## How strict is the need for these ## 1. I know - after all I was a performance engineer for a decade - that speed is important. And those extra mitigation flags are all about improved mitigations for speed. But TBH, that also makes them not strictly required for the function. 2. After all the CPU features we are talking about here are still rare. You only get them at the very latest CPUs. So the chances that an existing server Farm needs those changes desperately are low. This will mostly be for consideration of new setups, and they can/should use the new code of the new release. ## Availability ## 1. The majority of this code is upstream in 5.5 and we backported it to 5.4 for Eoan - so there is a Ubuntu release that can use this code already. 2. LTS users in Bionic (way more than Eoan I'd think) can get also access to it via the Ubuntu Cloud Archive [1]. And that is not only true for the now released 5.4, but when we release Ubuntu 20.04 there will be a new UCA along it containing all the final upstream fixes (not only our backports) - and that will be supported for an even longer time. ## Verdict ## I second your call on these patches after reading your summary, lets call the related libvirt backports Won't Fix for now. ## TODOs ## @Rafael - do you still have a TODO on the kernel side as there are tasks open and assigned? @Rafael - while I generally dislike raw qemu-cmdline in XML documenting an example as you suggested might be useful, will you come up with a draft for it? @Rafael/Christian - lets also talk with the Team about it to get everyone on the same page. [1]: https://wiki.ubuntu.com/OpenStack/CloudArchive ** Changed in: libvirt (Ubuntu Disco) Status: Opinion => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824559] Re: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency)
Hi @pieq, following your message I launched download of Ubuntu 19.10 image. I will test with live session as suggested (as I keep my laptop on LTS for the moment) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824559 Title: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849008] Re: bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849035 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Ready for Packaging - phase-changed: Monday, 21. October 2019 19:22 UTC + phase: Packaging + phase-changed: Tuesday, 22. October 2019 05:15 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-raspi2/pi-kernel: bug 1849007 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/1849008 Title: bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849008] Re: bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker
** Summary changed: - bionic/linux-raspi2: -proposed tracker + bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849008 Title: bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 I built a testing kernel, not only includes the fix for USB host, but also includes all new patches from https://github.com/raspberrypi/linux.git rpi-5.3.y branch (about 107 patches). I tested both arm64 and armhf kernels on Pi4 without HDMI monitor, everything works well. Could anybody help test these two kernels on Pi4 with HDMI monitor, Pi3 and Pi2 if you have any of them? After verifying the kernel will not introduce regression on Pi4/3/2, I will submit the patches to UBUNTU kernel. The new kernel could be downloaded: https://people.canonical.com/~hwang4/rpiv2/ To install and test the kernel: copy arm64 or armhf folders to rootfs of Pi, sudo dpkg -i linux-modules-.deb; sudo dpkg -i linux-image-xxx.deb;sudo reboot thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
I built a testing kernel, not only includes the fix for USB host, but also includes all new patches from https://github.com/raspberrypi/linux.git rpi-5.3.y branch (about 107 patches). I tested both arm64 and armhf kernels on Pi4 without HDMI monitor, everything works well. Could anybody help test these two kernels on Pi4 with HDMI monitor, Pi3 and Pi2 if you have any of them? After verifying the kernel will not introduce regression on Pi4/3/2, I will submit the patches to UBUNTU kernel. The new kernel could be downloaded: https://people.canonical.com/~hwang4/rpiv2/ To install and test the kernel: copy arm64 or armhf folders to rootfs of Pi, sudo dpkg -i linux-modules-.deb; sudo dpkg -i linux-image-xxx.deb;sudo reboot thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849044] Re: xenial/linux-raspi2: 4.4.0-1125.134 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849051 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Packaging - phase-changed: Monday, 21. October 2019 22:11 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 22. October 2019 04:54 UTC reason: - prepare-package: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: xenial/linux-raspi2/pi2-kernel: bug 1849043 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/1849044 Title: xenial/linux-raspi2: 4.4.0-1125.134 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849051] Re: xenial/linux: 4.4.0-167.196 -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 packages: main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Monday, 21. October 2019 20:17 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 22. October 2019 04:53 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait + promote-to-proposed: Pending -- ready for review trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 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/1849051 Title: xenial/linux: 4.4.0-167.196 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849035] Re: bionic/linux: 4.15.0-67.76 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Monday, 21. October 2019 19:20 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 22. October 2019 04:52 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849005 bionic/linux/pc-lowlatency-kernel: bug 1849006 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849034 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/1849035 Title: bionic/linux: 4.15.0-67.76 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849168] Re: [SRU] Missing build dep libsndfile1-dev discovered
** Description changed: [Impact] * Users have reported the inability to use soundfonts with Carla hosted synthesizer plugins * Backporting this to the stable release would fix the problem. * The upload simply adds libsndfile1-dev as a build dependency. [Test Case] * Add any soundfont-utilizing synthesizer plugin to Carla, patch audio out to system out, attempt to play notes either using a MIDI keyboard or using the canvas keyboard in Carla. Carla gives the following error: ad_open(): fatal: no decoder backend available * Using the same procedures after the libsndfile1-dev build dependency is added should result in actual notes being produced. [Regression Potential] - * None, simply adds a build dependency + * None, simply adds a build dependency and patch to existing package [Other Information] - * Upload includes a patch from upstream developer to fix compatibility + * Upload includes a patch from upstream developer to fix compatibility issues with lsp-plugins, and debian/rules has been modified to deal with FTBFS bug introduced by wine-development included in eoan. ** Description changed: [Impact] * Users have reported the inability to use soundfonts with Carla hosted synthesizer plugins * Backporting this to the stable release would fix the problem. - * The upload simply adds libsndfile1-dev as a build dependency. + * The upload simply adds libsndfile1-dev as a build dependency, also + includes an upstream patch from the author to fix incompatibilities with + lsp-plugins. [Test Case] * Add any soundfont-utilizing synthesizer plugin to Carla, patch audio out to system out, attempt to play notes either using a MIDI keyboard or using the canvas keyboard in Carla. Carla gives the following error: ad_open(): fatal: no decoder backend available * Using the same procedures after the libsndfile1-dev build dependency is added should result in actual notes being produced. [Regression Potential] * None, simply adds a build dependency and patch to existing package [Other Information] * Upload includes a patch from upstream developer to fix compatibility issues with lsp-plugins, and debian/rules has been modified to deal with FTBFS bug introduced by wine-development included in eoan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849168 Title: [SRU] Missing build dep libsndfile1-dev discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1849168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849254] [NEW] Noto Sans Mono Bold not available from /etc/fonts/local.conf
Public bug reported: I tried to change my monospace font to "Noto Sans Mono Bold" in /etc/fonts/local.conf but that didn't have an effect so I did a little digging. First I ran $ sudo fc-cache -f -v && sudo dpkg-reconfigure fontconfig fontconfig-config Which succeeded, then: $ fc-list :style=bold | grep -i notosansmono >/usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf: Noto Sans Mono:style=Bold So then: $fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf | less which seemed to return a normal looking result similar to: $fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Regular.ttf | less Then I ran: $ fc-match -s "monospace" | grep -i bold >DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold" >MathJax_Fraktur-Bold.otf: "MathJax_Fraktur" "Bold" >padmaa-Bold.1.1.ttf: "padmaa-Bold.1.1" "Bold.1.1" >DejaVuSans-BoldOblique.ttf: "DejaVu Sans" "Bold Oblique" Which obviously isn't right since it isn't in that list. Also: $fc-match -s "NotoSansMono" | grep -i notosansmono >NotoSansMono-Regular.ttf: "Noto Sans Mono" "Regular" My system is up to date and here is my version: $lsb_release -a lsb_release: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $uname -a >Linux 9343 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 >x86_64 x86_64 x86_64 GNU/Linux ** Affects: fonts-noto (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/1849254 Title: Noto Sans Mono Bold not available from /etc/fonts/local.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1849254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822026] Re: [Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in gp100/gf100 code)
Confirmed still not working with 19.10 (linux 5.3.0-18-generic) on the Precision 7530. It's actually even worse: now, I can't even boot. I'm just shown a black screen. If I select the Safe graphics boot option, I can boot properly. Editing the default boot command line to include `nouveau.modeset=0` works, but editing it to put `nouveau.runpm=0` instead fails (black screen). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822026 Title: [Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in gp100/gf100 code) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849044] Re: xenial/linux-raspi2: 4.4.0-1125.134 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849051 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Packaging phase-changed: Monday, 21. October 2019 22:11 UTC reason: prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-raspi2/pi2-kernel: bug 1849043 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/1849044 Title: xenial/linux-raspi2: 4.4.0-1125.134 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1281758] Re: re-installing maas-region-controller fails
I ran into this issue (FATAL: password authentication failed for user "maas") by running the command 'maas-region createadmin --username admin --password kNab4Q9fSa --email admin@localhost.localdimain' today as well. I solved the problem in the following way. 1, confirm database_pass is wQ3fxcdSH1aI root@maas-ha-2:~# grep -r 'pass' /etc/maas/regiond.conf database_pass: wQ3fxcdSH1aI 2, change md5 into trust temporarily, then restart postgresql by 'systemctl restart pacemaker' /etc/postgresql/9.5/main/pg_hba.conf local all alltrust 3, change the password of the user maas to wQ3fxcdSH1aI sudo su - maas psql -d maasdb -U maas maasdb=> alter user maas with password 'wQ3fxcdSH1aI'; 4, ok -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281758 Title: re-installing maas-region-controller fails To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1281758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849218] Re: maas errors with usb drive
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => MAAS (maas) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849218 Title: maas errors with usb drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1849218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849253] Re: apt-get install fails when UNRELATED package list is invalid
I have the same issue if I try apt instead of apt-get. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849253 Title: apt-get install fails when UNRELATED package list is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849253] Re: apt-get install fails when UNRELATED package list is invalid
$ apt-cache policy apt E: Encountered a section with no Package: header E: Problem with MergeList /var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages E: The package lists or status file could not be parsed or opened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849253 Title: apt-get install fails when UNRELATED package list is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849253] [NEW] apt-get install fails when UNRELATED package list is invalid
Public bug reported: 1) Description: Ubuntu 19.04 Release:19.04 2) unknown (see below) 3) Even when a package list from one source is invalid, I can still apt-get install and apt-get update packages from other sources, as long as they don't depend on packages in the bad list. 4) I can't install a package from *any* source, even the ones that still yield valid package lists. On Xubuntu 19.04, I have the following in my sources.list: deb https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main deb-src https://adoptopenjdk.jfrog.io/adoptopenjdk/deb/ disco main Currently those sources yield invalid package lists. However, installation of a package fails even when it comes from *another* source. $ sudo apt-get install stress Reading package lists... Error! E: Encountered a section with no Package: header E: Problem with MergeList /var/lib/apt/lists/adoptopenjdk.jfrog.io_adoptopenjdk_deb_dists_disco_main_binary-amd64_Packages E: The package lists or status file could not be parsed or opened. Shouldn't this affect only packages that come from the faulty package list or depend on ones that do? I get the same error when running $ apt-cache policy apt-get so I can't determine what version of apt-get I'm encountering this bug in. ** Affects: apt (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/1849253 Title: apt-get install fails when UNRELATED package list is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849253] Re: apt-get install fails when UNRELATED package list is invalid
#1848974 may be a duplicate of this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849253 Title: apt-get install fails when UNRELATED package list is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 853333] Re: default window too large for wsvga netbook display resolution
[Expired for subdownloader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: subdownloader (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/85 Title: default window too large for wsvga netbook display resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subdownloader/+bug/85/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840514] Re: amdgpu on RX 460 in 18.04.3 does not change state
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (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/1840514 Title: amdgpu on RX 460 in 18.04.3 does not change state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840962] Re: No touchpad detected Lenovo P50
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (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/1840962 Title: No touchpad detected Lenovo P50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840963] Re: 500 OOPS: unrecognised variable in config file: ssl_tlsv1_1
[Expired for vsftpd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vsftpd (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/1840963 Title: 500 OOPS: unrecognised variable in config file: ssl_tlsv1_1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1840963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846127] Re: xenial/linux-hwe-edge: 4.15.0-66.75~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846130 packages: meta: linux-meta-hwe-edge - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:43 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 04:20 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1846127 Title: xenial/linux-hwe-edge: 4.15.0-66.75~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836858] Re: i915: Display flickers during "flickerfree" boot (BIOS logo on a black background)
Also keep in mind that the duration of the flicker here depends on the model of monitor in use. Some laptops/monitors might be super-fast and not black-out when the programmed mode changes. But in my experience most will. Sometimes quickly and sometimes slowly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: i915: Display flickers during "flickerfree" boot (BIOS logo on a black background) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841024] Re: sreen captured
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (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/1841024 Title: sreen captured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846121] Re: xenial/linux-azure-edge: 4.15.0-1061.66 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846123 packages: meta: linux-meta-azure-edge - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:42 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 04:20 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1846121 Title: xenial/linux-azure-edge: 4.15.0-1061.66 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849003] Re: disco/linux: 5.0.0-33.35 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Tuesday, 22. October 2019 02:07 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:failed,signed:depwait trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1849000 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 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/1849003 Title: disco/linux: 5.0.0-33.35 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836858] Re: CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER needed for flickerfree boot
No that kernel did not fix the bug :( ** Summary changed: - CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER needed for flickerfree boot + i915: Display flickers during "flickerfree" boot (BIOS logo on a black background) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: i915: Display flickers during "flickerfree" boot (BIOS logo on a black background) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836858] Re: i915: Display flickers during "flickerfree" boot (BIOS logo on a black background)
$ uname -a Linux kab 5.3.0-19-generic #20~lp1836858 SMP Fri Oct 18 12:09:47 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: i915: Display flickers during "flickerfree" boot (BIOS logo on a black background) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841736] Re: Intel Killer(R) Wi-Fi 6 AX1650i/AX1650s 160MHz Wireless Network Adapter (201NGW) [8086:34f0] subsystem [1a56:1651] not supported
This has been automatically included in eoan 5.3.0-10. ** Changed in: linux-oem-osp1 (Ubuntu Eoan) Status: New => Fix Released ** Changed in: linux-oem-osp1 (Ubuntu Eoan) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841736 Title: Intel Killer(R) Wi-Fi 6 AX1650i/AX1650s 160MHz Wireless Network Adapter (201NGW) [8086:34f0] subsystem [1a56:1651] not supported To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1841736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847930] Re: bionic/linux-gke-5.0: 5.0.0-1023.23~18.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846086 packages: main: linux-gke-5.0 meta: linux-meta-gke-5.0 signed: linux-signed-gke-5.0 - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 15:11 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 04:05 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy replaces: bug 1847670 trackers: bionic/linux-gke-5.0/gke-kernel: bug 1847928 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/1847930 Title: bionic/linux-gke-5.0: 5.0.0-1023.23~18.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846126] Re: xenial/linux-gcp: 4.15.0-1047.50 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846131 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:29 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 04:09 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: xenial/linux-gcp/gcp-kernel: bug 1846124 xenial/linux-gcp/gke-kernel: bug 1846125 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/1846126 Title: xenial/linux-gcp: 4.15.0-1047.50 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846123] Re: xenial/linux-azure: 4.15.0-1061.66 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846131 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:29 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 04:08 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: trusty/linux-azure: bug 1846122 xenial/linux-azure-edge: bug 1846121 xenial/linux-azure/azure-kernel: bug 1846120 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/1846123 Title: xenial/linux-azure: 4.15.0-1061.66 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846130] Re: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846131 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:30 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 04:09 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: xenial/linux-deeplens: bug 1846128 xenial/linux-hwe-edge: bug 1846127 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/1846130 Title: xenial/linux-hwe: 4.15.0-66.75~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
I've pushed a new version to the same PPA based on 5.3.0-19. Please have an update and give it a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843743] Re: klibc ftbfs in eoan
This bug was fixed in the package klibc - 2.0.6-1ubuntu2 --- klibc (2.0.6-1ubuntu2) eoan; urgency=medium * Fix FTBFS on eoan and later with new linux and gcc (LP: #1843743) - cf-protection.patch: Disable cf-protection for syscalls stub. - mman-include.patch: Adjust for changes to linux headers in 5.3. -- Adam Conrad Mon, 21 Oct 2019 15:39:37 -0600 ** Changed in: klibc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849214] Re: "nvidia on-demand" mode does not support external displays
** Also affects: nvidia-graphics-drivers (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/1849214 Title: "nvidia on-demand" mode does not support external displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1849214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712938] Re: error while loading shared libraries: cannot open shared object file: No such file or directory
Sorry to drag up a very old bug like this - but this still seems to be an issue in new ubuntu/debian based distributions. I ran into this issue when using llvm-strip and it doesn't preserve .ARM.attributes - I have written a patch against llvm-strip that's being discussed here: https://reviews.llvm.org/D69188 But this is something that seems to be introduced in the patchset used and not upstream glibc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712938 Title: error while loading shared libraries: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1712938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
Dropped the bionic task until such time as this becomes a reproducible and testable bug there. ** No longer affects: mutter (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712938] Re: error while loading shared libraries: cannot open shared object file: No such file or directory
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glibc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712938 Title: error while loading shared libraries: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1712938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
I am having the same problem with 19.04 and an Apple Magic Pad. I have read in the links below that a solution would be to disable the config HID_BATTERY_STRENGTH. It says: "Rebuild the kernel with CONFIG_HID_BATTERY_STRENGTH=N and the issue disappears, along with battery status reporting", but I have never built a kernel before... Someone has tried or can help? https://bugzilla.kernel.org/show_bug.cgi?id=103631 https://linuxlists.cc/l/15/linux- bluetooth/t/3170957/apple_magicmouse_disconnects ** Bug watch added: Linux Kernel Bug Tracker #103631 https://bugzilla.kernel.org/show_bug.cgi?id=103631 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.
** Changed in: nginx (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743592 Title: NGINX fails to start/install/upgrade if IPv6 is completely disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849251] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:set_workspace_state
*** This bug is a duplicate of bug 1849249 *** https://bugs.launchpad.net/bugs/1849249 ** This bug has been marked a duplicate of bug 1849249 gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849251 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:set_workspace_state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848324] Re: Integrate Fixes from Mellanox 2019-10-16
** Changed in: linux-bluefield (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848324 Title: Integrate Fixes from Mellanox 2019-10-16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1848324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849251] [NEW] /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:set_workspace_state
*** This bug is a duplicate of bug 1849249 *** https://bugs.launchpad.net/bugs/1849249 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849251 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:set_workspace_state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Thanks for the bug report. Tracking in: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b ** Summary changed: - gnome-shell crashed with SIGABRT + gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) ** Information type changed from Private to Public ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Description changed: + https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b + gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) - * I move the find window to another monitor, + * I move the find window to another monitor, * I type in some text in the find window and press ENTER (or click the Next button) Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. If the find window opens on the second monitor (so I don't need to move it), gnome-shell still crashes. gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: - LANG=en_AU.UTF-8 - LANGUAGE=en_AU:en - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + LANGUAGE=en_AU:en + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849051] Re: xenial/linux: 4.4.0-167.196 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 21. October 2019 20:17 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 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/1849051 Title: xenial/linux: 4.4.0-167.196 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9
** Changed in: linux (Ubuntu) Status: In Progress => Incomplete ** Changed in: ubuntu-power-systems Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848193 Title: Fixup tlbie vs store ordering issue on POWER9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849035] Re: bionic/linux: 4.15.0-67.76 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 21. October 2019 19:20 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1849012 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849005 bionic/linux/pc-lowlatency-kernel: bug 1849006 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849034 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/1849035 Title: bionic/linux: 4.15.0-67.76 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Downgraded to 2.02 and everything works again. Major difference in debug output on 2.02 is the line which says: 2.02: shim bla bla not available shim_lock bla bla linuxefi_secure_validate: 0 2.04: SecureBoot: 0 SetupMode: 1 secure boot not enabled, not validating bla bla linuxefi_secure_validate: 1 If you didn't notice the difference - 2.02 detects that Secure Boot is disabled and sets: linuxefi_secure_validate: 0 2.04 also detects that Secure Boot is disabled, however sets: linuxefi_secure_validate: 1. This issue looks almost exactly the same as: https://github.com/aarch64-laptops/build/issues/18 and as Bug 1839317 Please confirm and link with 1839317. ** Bug watch added: github.com/aarch64-laptops/build/issues #18 https://github.com/aarch64-laptops/build/issues/18 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847063] Update by hwe-bug-checker
This issue has been fix in linux-oem 4.15.0-1059.68 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847063 Title: Fix non-working Realtek USB ethernet after system resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
For the sake of testing I've updated to the latest grub from 19.10 (2.04-1ubuntu12) and I can't boot Windows anymore. My exact steps were: 0. Ubuntu 19.10 with grub from 19.04. Everything works 1. Move /etc/grub.d/07_os-prober back to /etc/grub.d/30_os-prober to rule this change out 2. sudo apt update && sudo apt dist-upgrade 3. sudo grub-install /dev/sda 4. sudo update-grub 5. Reboot 6. Can't boot Windows anymore I've compared grub config from 2.02 to 2.04. They look almost exactly the same. The only differences are: - set vt_handoff=vt.handoff=1 + set vt_handoff=vt.handoff=7 and +### BEGIN /etc/grub.d/10_linux_zfs ### +### END /etc/grub.d/10_linux_zfs ### Windows part config: menuentry 'Windows Boot Manager (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-efi-CAC2-FF0C' { insmod part_gpt insmod fat set root='hd0,gpt1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 CAC2-FF0C else search --no-floppy --fs-uuid --set=root CAC2-FF0C fi chainloader /EFI/Microsoft/Boot/bootmgfw.efi } I've recorded video of boot process with "set debug=all" grub config. Send me a message through https://launchpad.net/~xeron- oskom/+contactuser if you want to see it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847063] Update by hwe-bug-checker
This issue has been fix in linux-oem 4.15.0-1059.68 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847063 Title: Fix non-working Realtek USB ethernet after system resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847678] Re: nvidia-dkms-435 435.21-0ubuntu1: nvidia kernel module failed to build [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
*** This bug is a duplicate of bug 1830961 *** https://bugs.launchpad.net/bugs/1830961 This bug is already fixed in current Ubuntu versions (see bug 1830961) The only problem here is that you still have an old kernel installed that's not compatible with gcc-9. Just uninstall kernel 4.15.0-1018-oracle. ** Summary changed: - nvidia-dkms-435 435.21-0ubuntu1: nvidia kernel module failed to build + nvidia-dkms-435 435.21-0ubuntu1: nvidia kernel module failed to build [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible] ** This bug has been marked a duplicate of bug 1830961 Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847678 Title: nvidia-dkms-435 435.21-0ubuntu1: nvidia kernel module failed to build [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1847678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848750] Re: Eoan update: 5.3.7 upstream stable release
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848750 Title: Eoan update: 5.3.7 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
Yeah it sounds like the XPS 9575 is the main model affected. Also Precision 5530 (comment #14). ** Summary changed: - [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot + [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard & touchpad not working at gdm screen after boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845602] Re: Initial setup screen has thick white borders
I installed the final image on this device a couple of times and could not reproduce the issue. Marking this as Invalid. ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845602 Title: Initial setup screen has thick white borders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1845602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Bug 1839317 looks too similar to ignore the possibility of the same underlying issue. There's other person there besides me who reports the same behavior on amd64. My Windows bootloader is fine. I can boot Windows using my motherboard's EFI boot menu selector. I can boot Windows if I downgrade GRUB to the version from Ubuntu 19.04 (2.02+dfsg1-12ubuntu2). My setup is EFI + GPT. Secure Boot is disabled. Partitions: Device Start End Sectors Size Type /dev/sda1 2048821247819200 400M EFI System /dev/sda2 821248 1083391262144 128M Microsoft reserved /dev/sda31083392 210209396 209126005 99.7G Microsoft basic data (WINDOWS 10 SYSTEM IS HERE) /dev/sda4 210210816 211257343 1046528 511M Windows recovery environment /dev/sda5 211257344 420513791 209256448 99.8G Microsoft basic data /dev/sda6 420513792 445679615 25165824 12G Linux filesystem (UBUNTU ROOT, EXT4) /dev/sda7 445679616 468860927 23181312 11.1G Linux filesystem (UBUNTU HOME, XFS) Mounts: /dev/sda1 on /boot/efi /dev/sda6 on / /dev/sda7 on /home /etc/default/grub custom options: GRUB_TIMEOUT=5 GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.show_status=1" GRUB_GFXMODE=2560x1440 GRUB_DISABLE_RECOVERY="true" GRUB_DISABLE_SUBMENU=y GRUB_GFXPAYLOAD_LINUX=keep GRUB_FONT=/boot/grub/terminus-32b.pf2 /etc/grub.d/30_os-prober renamed to /etc/grub.d/07_os-prober -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848360] Re: [AMD Raven Ridge] Screen always returns to full brightness after wake up
Also there is one more thing weird. Before I fresh install the 19.10 beta,I used Ubuntu 19.04 which was upgraded from 18.04.There was same issue at first when I fresh installed 18.04,but then it's gone after upgrading to 19.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848360 Title: [AMD Raven Ridge] Screen always returns to full brightness after wake up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824559] Re: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency)
Device: XPS 13 7390 Image: 19.10 Final Kernel: 5.3.0-19-generic Mice tested: Logitech M585, Microsoft Designer Mouse The issue is gone. @wysiwyg31: could you give it a try? You can boot a live session of Ubuntu 19.10 on your device and try to pair your Bluetooth mouse. If it works for you, I'll mark the issue as 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/1824559 Title: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845454] Re: Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works)
Fixed on Dell XPS 13 7390 with 5.3.0-19. ** Tags added: cqa-verified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845454 Title: Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
Posted again with a proper subscription instead of guest post: https://lists.ubuntu.com/archives/kernel-team/2019-October/104898.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848984] Re: disco/linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 03:47 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:10 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-aws-5.0: bug 1848983 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/1848984 Title: disco/linux-aws: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838246] Re: Nginx 1.14.0 fails to start if ipv6 support on host is disabled
*** This bug is a duplicate of bug 1743592 *** https://bugs.launchpad.net/bugs/1743592 ** Bug watch added: Debian Bug tracker #942817 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817 ** Also affects: nginx (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838246 Title: Nginx 1.14.0 fails to start if ipv6 support on host is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/nginx/+bug/1838246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848995] Re: disco/linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 04:08 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:11 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-gcp: bug 1848992 bionic/linux-gke-5.0: bug 1848994 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/1848995 Title: disco/linux-gcp: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848999] Re: disco/linux-snapdragon: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 04:08 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:11 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified 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/1848999 Title: disco/linux-snapdragon: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848989] Re: disco/linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 04:01 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:10 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-azure: bug 1848987 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/1848989 Title: disco/linux-azure: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.
Debian proposal patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=942817;filename=0001-Allow-nginx-to-start-on-ipv6-disabled-system.patch;msg=15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743592 Title: NGINX fails to start/install/upgrade if IPv6 is completely disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849000] Re: bionic/linux-hwe: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 04:09 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:12 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified 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/1849000 Title: bionic/linux-hwe: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849002] Re: bionic/linux-bluefield: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-bluefield meta: linux-meta-bluefield - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 04:09 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:12 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified 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/1849002 Title: bionic/linux-bluefield: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849072] Re: [snap] no access to softlinked folders in home directory
Yes, works fine. Not sure if it's worth patching the ERR_FILE_NOT_FOUND page - to somehow explain snap permissions and how to adjust them.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849072 Title: [snap] no access to softlinked folders in home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.
Debian bug discussion: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817 ** Bug watch added: Debian Bug tracker #942817 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817 ** Also affects: nginx (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817 Importance: Unknown Status: Unknown ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743592 Title: NGINX fails to start/install/upgrade if IPv6 is completely disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849001] Re: bionic/linux-oem-osp1: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: lrm: linux-restricted-modules-oem-osp1 main: linux-oem-osp1 meta: linux-meta-oem-osp1 signed: linux-signed-oem-osp1 - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 04:09 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:12 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified 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/1849001 Title: bionic/linux-oem-osp1: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848996] Re: disco/linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 04:08 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:11 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified 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/1848996 Title: disco/linux-kvm: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848998] Re: disco/linux-oracle: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 04:08 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:11 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-oracle-5.0: bug 1848997 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/1848998 Title: disco/linux-oracle: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849183] Re: Bluetooth devices doesn't get listed while turn off and then on
** Package changed: alsa-driver (Ubuntu) => gnome-control-center (Ubuntu) ** Also affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Also affects: bluez (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/1849183 Title: Bluetooth devices doesn't get listed while turn off and then on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1849183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846064] Re: xenial/linux-snapdragon: 4.4.0-1128.136 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846069 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:28 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 02:10 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1846063 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/1846064 Title: xenial/linux-snapdragon: 4.4.0-1128.136 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846060] Re: xenial/linux-kvm: 4.4.0-1060.67 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846069 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:13 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 02:09 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1846060 Title: xenial/linux-kvm: 4.4.0-1060.67 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846062] Re: xenial/linux-raspi2: 4.4.0-1124.133 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846069 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:13 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 02:09 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: xenial/linux-raspi2/pi2-kernel: bug 1846061 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/1846062 Title: xenial/linux-raspi2: 4.4.0-1124.133 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Clicking Activities in the corner doesn't work in Xorg sessions
I will need to debug this more in detail. If we find it is Xorg giving us the negative pointer coordinates then it should be fixed there. But it might just be a mutter bug... ** Tags added: rls-ee-incoming ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846069] Re: xenial/linux: 4.4.0-166.195 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: Holding before Promote to Security - phase-changed: Monday, 21. October 2019 13:12 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 22. October 2019 02:06 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: trusty/linux-aws: bug 1846066 trusty/linux-lts-xenial: bug 1846067 xenial/linux-aws: bug 1846059 xenial/linux-fips: bug 1846065 xenial/linux-kvm: bug 1846060 xenial/linux-raspi2: bug 1846062 xenial/linux-snapdragon: bug 1846064 xenial/linux/caracalla-kernel: bug 1846054 xenial/linux/pc-kernel: bug 1846055 xenial/linux/stlouis-kernel: bug 1846057 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/1846069 Title: xenial/linux: 4.4.0-166.195 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848981] Re: disco/linux-raspi2: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Holding before Packaging - phase-changed: Monday, 21. October 2019 03:46 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 22. October 2019 02:10 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified 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/1848981 Title: disco/linux-raspi2: -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849003] Re: disco/linux: 5.0.0-33.35 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Monday, 21. October 2019 17:55 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 22. October 2019 02:07 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1849000 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 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/1849003 Title: disco/linux: 5.0.0-33.35 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849135] Re: Activities button does not respond to clicks on a specific pixel
Thanks for the bug report and screenshot. That does confirm it is https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 ** Tags added: eoan ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Summary changed: - Activities button does not respond to clicks on a specific pixel + Clicking Activities in the corner doesn't work in Xorg sessions ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849135 Title: Clicking Activities in the corner doesn't work in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849168] Re: [SRU] Missing build dep libsndfile1-dev discovered
Fixed FTB errors. ** Description changed: [Impact] - * Users have reported the inability to use soundfonts with Carla hosted + * Users have reported the inability to use soundfonts with Carla hosted synthesizer plugins - * Backporting this to the stable release would fix the problem. + * Backporting this to the stable release would fix the problem. - * The upload simply adds libsndfile1-dev as a build dependency. + * The upload simply adds libsndfile1-dev as a build dependency. [Test Case] - * Add any soundfont-utilizing synthesizer plugin to Carla, patch audio + * Add any soundfont-utilizing synthesizer plugin to Carla, patch audio out to system out, attempt to play notes either using a MIDI keyboard or using the canvas keyboard in Carla. Carla gives the following error: ad_open(): fatal: no decoder backend available - * Using the same procedures after the libsndfile1-dev build dependency + * Using the same procedures after the libsndfile1-dev build dependency is added should result in actual notes being produced. [Regression Potential] - * None, simply adds a build dependency. + * None, simply adds a build dependency + + [Other Information] + + * Upload includes a patch from upstream developer to fix compatibility + issues with lsp-plugins, and debian/rules has been modified to deal with + FTBFS bug introduced by wine-development included in eoan. ** Changed in: carla (Ubuntu) Status: In Progress => Fix Committed ** Changed in: carla (Ubuntu) Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849168 Title: [SRU] Missing build dep libsndfile1-dev discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1849168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849051] Re: xenial/linux: 4.4.0-167.196 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 21. October 2019 20:17 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 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/1849051 Title: xenial/linux: 4.4.0-167.196 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849157] Re: Default sound output device is never the expected one
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1847570, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1847570 PulseAudio automatically switches to HDMI sound output on login -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849157 Title: Default sound output device is never the expected one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
XPS 9575 isn't (currently) available for purchase with Ubuntu. So yes, it's below the radar for something that is typically tested, tracked, or fixed from a BIOS or validation team perspective. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849232] [NEW] fusermount -u in bash script prepends /home to path if resource is busy
Public bug reported: Kindly see this question in StackExchange: https://superuser.com/q/1494196/253105 If a busy resource path is passed such as `fusermount -u /path/to/busy/resource`, fusermount gives the following message: `fusermount: failed to unmount /home/path/to/busy/resource: Device or resource busy` It prepends `/home` to the path in the warning message. Tested on Ubuntu 18.04 from package util-linux 2.30.1-0ubuntu4. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849232 Title: fusermount -u in bash script prepends /home to path if resource is busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1849232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
@Christian, I'm flagging the libvirt SRUs as Opinion. So far I have done quite a lot cherry-picks and backports identifying all the structures that have changed and I'm not currently seeing how this can be done as a SRU (even for Disco). There are quite a few data model changes to how libvirt was acquiring CPU features (and, now, missing features) that simply wont fit into SRU rules. The base need for the features would be: commit c145b660b8225f73db16660461077ef931730939 Author: Jiri Denemark Date: Fri Jun 7 09:07:10 2019 cpu_conf: Introduce virCPUDefFilterFeatures This new internal API can be used for in place filtering of CPU features in virCPUDef. Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko commit 2a4c23210674b453f91569f0f4b9fd5ebe8d7906 Author: Jiri Denemark Date: Mon Jun 10 11:46:10 2019 qemu: Probe for max-x86_64-cpu type We will use it to check whether QEMU supports a specific CPU property. Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko commit 0d254bce4ec6fd62c0277d24e28bf018a4c6cb37 Author: Jiri Denemark Date: Mon Jun 10 11:49:22 2019 qemu: Probe for "unavailable-features" CPU property It is similar to "filtered-features" property, which reports CPUID bits corresponding to disabled features, but more general. The "unavailable-features" property supports both CPUID and MSR features by listing their names. Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko commit 4e6f58b8d55d44fa9f80736b2745b44710f6e25a Author: Jiri Denemark Date: Wed Jun 19 14:01:30 2019 conf: Introduce virCPUDefCheckFeatures This API can be used to check whether a CPU definition contains features matching a given filter. Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko commit b8e086a570b14b1f83fc07e25df6da758abe7706 Author: Jiri Denemark Date: Wed Jun 19 16:58:01 2019 cpu_x86: Turn virCPUx86DataIteratorInit into a function Until now, this was a macro usable for direct initialization when a variable is defined. Turning the macro into a function makes it more general. Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko < compiles good > Then we would need the backport of: cpu_x86: Introduce virCPUx86DataItem container struct The following patches introduce CPU features read from MSR in addition to those queried via CPUID instruction. Let's introduce a container struct which will be able to describe either feature type. Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko AND all the ones bellow: fcf4846a6b cpu_x86: Add support for storing MSR features in CPU map 370177e2f6 cpu_x86: Store virCPUx86DataItem content in union 10b80165db cpu_x86: Make x86cpuidMatch more general 2eea67a98e cpu_x86: Make x86cpuidMatchMasked more general da1efddfa6 cpu_x86: Make x86cpuidAndBits more general 4e3cab2d00 cpu_x86: Make x86cpuidClearBits more general 9c6f00fc33 cpu_x86: Make x86cpuidSetBits more general 559ccd7815 cpu_x86: Introduce virCPUx86DataCmp 0fdc0ad84c cpu_x86: Simplify x86DataAdd 3eff71a2d5 cpu_x86: Rename virCPUx86VendorToCPUID 8f1a8ce397 cpu_x86: Rename virCPUx86DataAddCPUID ce42042577 cpu_x86: Rename virCPUx86DataAddCPUIDInt 95accfa7fa cpu_x86: Rename virCPUx86CPUIDSorter 609f467f13 cpu_x86: Rename x86DataCpuid 5655b83139 cpu_x86: Rename x86DataCpuidNext function 6c22b329d5 cpu_x86: Rename virCPUx86DataItem variables c02d70d52e cpu_x86: Rename virCPUx86Vendor.cpuid AT LEAST to compile the virCPUx86DataItem container feature. Continuing, we would, still, need: commit bcfed7f1c84cbff21d129a79cbd675b0cd51613c Author: Jiri Denemark Date: Wed Jun 19 16:59:12 2019 cpu_x86: Introduce virCPUx86FeatureFilter*MSR This functions may be used as a virCPUDefFeatureFilter callbacks for virCPUDefCheckFeatures, virCPUDefFilerFeatures, and similar functions to select (virCPUx86FeatureFilterSelectMSR) or drop (virCPUx86FeatureFilterDropMSR) features reported via MSR. Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko commit 56b254dccc96b7339494812c9df07ccf6af3da95 Author: Jiri Denemark Date: Fri Mar 22 12:52:21 2019 cpu_x86: Read CPU features from IA32_ARCH_CAPABILITIES MSR This is used by the host capabilities code to construct host CPU definition. Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko commit c8ec678fd9d97189667c0121f48a220dd26856b7 Author: Jiri Denemark Date: Thu Mar 14 11:44:38 2019 cpu_map: Introduce IA32_ARCH_CAPABILITIES MSR features Signed-off-by: Jiri Denemark Reviewed-by: Ján Tomko commit 8eb4a89f5f7973f50aa8b6fa0b1a45b825dda208 Author: Jiri Denemark Date: Wed Jun 19 16:59:49 2019 qemu: Forbid MSR features with old QEMU Without "unavailable-features" CPU property we cannot properly detect whether a specific MSR feature we asked for (either explicitly or implicitly via a CPU model) was disabled by QEMU for some
[Bug 1849050] Re: 19.10 fails to allow login from desktop if enable automatically login
*** This bug is a duplicate of bug 1845801 *** https://bugs.launchpad.net/bugs/1845801 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1845801, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1845801 [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849050 Title: 19.10 fails to allow login from desktop if enable automatically login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1849050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774843] Re: apport python exception handler messes up python3.7
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1774843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store
On Mon, Oct 21, 2019 at 07:57:19PM -, Olivier Tilloy wrote: > Can you check whether the password-manager-service interface is > connected? > snap connections chromium | grep password Output is: $ snap connections chromium | grep password password-manager-service chromium:password-manager-service - - $ So I think that means it is connected? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849160 Title: after deb->snap transition, chromium no longer sees local password store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848741] Re: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u
Thanks but that didn't attach as much info as I had hoped. Please run: lspci -k > lspcik.txt dmesg > dmesg.txt and then attach the files 'lspcik.txt' and 'dmesg.txt'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848741 Title: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs