[Bug 1929188] [NEW] Grub install failed in dual boot
Public bug reported: I've been trying to dual boot ubuntu along windows 10 but so far, install always encounters a fatal error when it comes to the installation of grub2. Now, I can't even boot Windows 10. Installation of Ubuntu 20.04.02 Output of lscpi -v H/W path Device Class Description === system To be filled by O.E.M. (To be filled by O.E.M.) /0 bus CRESCENTBAY /0/0memory 64KiB BIOS /0/3d memory 32KiB L1 cache /0/3e memory 32KiB L1 cache /0/3f memory 256KiB L2 cache /0/40 memory 4MiB L3 cache /0/41 processor Intel(R) Core(TM) i7-4560U CPU @ 1.60GHz /0/43 memory 8GiB System Memory /0/43/0 memory 8GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) /0/43/1 memory DIMM [empty] /0/100 bridge Haswell-ULT DRAM Controller /0/100/2display Haswell-ULT Integrated Graphics Controller /0/100/3multimedia Haswell-ULT HD Audio Controller /0/100/14 bus 8 Series USB xHCI HC /0/100/14/0 usb2 bus xHCI Host Controller /0/100/14/0/1 storage Cruzer Blade /0/100/14/0/7 bus USB2.0 Hub /0/100/14/0/7/1 input HP Basic USB Keyboard /0/100/14/0/7/2 input USB Receiver /0/100/14/0/8 storage USB Storage /0/100/14/1 usb3 bus xHCI Host Controller /0/100/1b multimedia 8 Series HD Audio Controller /0/100/1c bridge 8 Series PCI Express Root Port 1 /0/100/1c.2 bridge 8 Series PCI Express Root Port 3 /0/100/1c.2/0enp2s0 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller /0/100/1c.3 bridge 8 Series PCI Express Root Port 4 /0/100/1c.3/0enp3s0 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller /0/100/1c.5 bridge 8 Series PCI Express Root Port 6 /0/100/1c.5/0wlp4s0 network AR93xx Wireless Network Adapter /0/100/1d bus 8 Series USB EHCI #1 /0/100/1d/1 usb1 bus EHCI Host Controller /0/100/1d/1/1 bus USB hub /0/100/1f bridge 8 Series LPC Controller /0/100/1f.2 storage 8 Series SATA Controller 1 [AHCI mode] /0/100/1f.3 bus 8 Series SMBus Controller /0/1system PnP device PNP0c02 /0/2system PnP device PNP0c02 /0/3system PnP device PNP0b00 /0/4generic PnP device INT3f0d /0/5system PnP device PNP0c02 /0/6system PnP device PNP0c02 /0/7 scsi2 storage /0/7/0.0.0 /dev/sda disk1TB WDC WD10JPVX-22J /0/7/0.0.0/1 /dev/sda1 volume 579MiB Windows NTFS volume /0/7/0.0.0/2 /dev/sda2 volume 686GiB Windows NTFS volume /0/7/0.0.0/4 /dev/sda4 volume 244GiB Extended partition /0/7/0.0.0/4/5 /dev/sda5 volume 7812MiB Linux swap volume /0/7/0.0.0/4/6 /dev/sda6 volume 177GiB EXT4 volume /0/7/0.0.0/4/7 /dev/sda7 volume 1429MiB Windows FAT volume /0/7/0.0.0/4/8 /dev/sda8 volume 57GiB EXT4 volume /0/8 scsi3 storage /0/8/0.0.0 /dev/sdb disk15GB Cruzer Blade /0/8/0.0.0/0 /dev/sdb disk15GB /0/8/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT volume /0/8/0.0.0/0/3 /dev/sdb3 volume 11GiB EXT4 volume /0/9 scsi4 storage /0/9/0.0.0 /dev/sdc diskSTORAGE DEVICE /0/9/0.0.0/0 /dev/sdc disk ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 Date: Fri May 21 11:17:59 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script
FWIW, I'm doing canonistack arm64 testing now, by upgrading the image, then upgrading to proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928674 Title: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script
I think we discussed this yesterday that we need to properly test this. A smoke test on amd64 is not adequate, we also need to ensure additionally that - there are no regressions on arm64 install update in canonistack server and reboot it and make sure it boots. - there are no regressions in (maas) netbooting. I don't know how to verify nicely. I have a script you can point at shim and grub efi binaries to boot them similar to MAAS, but there might be more regressions, I clearly can't cover them all :) Due to the toolchain being different in the rebuilds happening in bionic/focal instead of hirsute, with much older binutils, and missing patches in gcc-8 likely. Because we know that at least shim did not work with old toolchain at all, so are a bit scared :D ** Tags removed: verification-done-bionic verification-done-xenial ** Tags added: verification-needed-bionic verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928674 Title: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1928674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929179] [NEW] [SRU] ceph 15.2.12
Public bug reported: [Impact] This release fixes several bugs. We would like to make sure all of our users have access to these improvements. The update contains the following package updates: * ceph 15.2.12 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStackUpdates In order to avoid regression of existing users, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Upstream release announcement] V15.2.12 OCTOPUS This is a hotfix release addressing a number of security issues and regressions. We recommend all users update to this release. CHANGELOG mgr/dashboard: fix base-href: revert it to previous approach (issue#50684, Avan Thakkar) mgr/dashboard: fix cookie injection issue (CVE-2021-3509: Dashboard XSS via token cookie, Ernesto Puerta) rgw: RGWSwiftWebsiteHandler::is_web_dir checks empty subdir_name (CVE-2021-3531: Swift API denial of service, Felix Huettner) rgw: sanitize r in s3 CORSConfiguration’s ExposeHeader (CVE-2021-3524: HTTP header injects via CORS in RGW, Sergey Bobrov, Casey Bodley) ** Affects: cloud-archive Importance: Undecided Status: Invalid ** Affects: cloud-archive/ussuri Importance: High Status: Triaged ** Affects: ceph (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ceph (Ubuntu Focal) Importance: High Status: Triaged ** Affects: ceph (Ubuntu Groovy) Importance: High Status: Triaged ** Also affects: ceph (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu Focal) Status: New => Triaged ** Changed in: ceph (Ubuntu Groovy) Status: New => Triaged ** Changed in: ceph (Ubuntu) Status: New => Invalid ** Changed in: ceph (Ubuntu Groovy) Importance: Undecided => High ** Changed in: ceph (Ubuntu Focal) Importance: Undecided => High ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3509 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3531 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3524 ** Description changed: - TBC + Upstream release announcement: + + V15.2.12 OCTOPUS + + This is a hotfix release addressing a number of security issues and + regressions. We recommend all users update to this release. + + + CHANGELOG + mgr/dashboard: fix base-href: revert it to previous approach (issue#50684, Avan Thakkar) + + mgr/dashboard: fix cookie injection issue (CVE-2021-3509: Dashboard XSS + via token cookie, Ernesto Puerta) + + rgw: RGWSwiftWebsiteHandler::is_web_dir checks empty subdir_name + (CVE-2021-3531: Swift API denial of service, Felix Huettner) + + rgw: sanitize r in s3 CORSConfiguration’s ExposeHeader (CVE-2021-3524: + HTTP header injects via CORS in RGW, Sergey Bobrov, Casey Bodley) ** Description changed: - Upstream release announcement: + [Impact] + This release fixes several bugs. We would like to make sure all of our users have access to these improvements. + + The update contains the following package updates: + +* ceph 15.2.11 + + [Test Case] + The following SRU process was followed: + + https://wiki.ubuntu.com/OpenStackUpdates + + In order to avoid regression of existing users, the OpenStack team will + run their continuous integration test against the packages that are in + -proposed. A successful run of all available tests will be required + before the proposed packages can be let into -updates. + + The OpenStack team will be in charge of attaching the output summary of + the executed tests. The OpenStack team members will not mark + ‘verification-done’ until this has happened. + + [Regression Potential] + In order to mitigate the regression potential, the results of the + aforementioned tests are attached to this bug. + + [Upstream release announcement] V15.2.12 OCTOPUS This is a hotfix release addressing a number of security issues and regressions. We recommend all users update to this release. - CHANGELOG mgr/dashboard: fix base-href: revert it to previous approach (issue#50684, Avan Thakkar) mgr/dashboard: fix cookie injection issue (CVE-2021-3509: Dashboard XSS via token cookie, Ernesto Puerta) rgw: RGWSwiftWebsiteHandler::is_web_dir checks empty subdir_name (CVE-2021-3531: Swift API denial of service, Felix Huettner) rgw: sanitize r in s3 CORSConfiguration’s ExposeHeader (CVE-2021-3524: HTTP header
[Bug 1929180] [NEW] backport-iwlwifi-dkms/8613-0ubuntu2 ADT test failure with linux-unstable/5.13.0-3.3
Public bug reported: This is a scripted bug report about ADT failures while running backport- iwlwifi-dkms tests for linux-unstable/5.13.0-3.3 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/amd64/b/backport-iwlwifi-dkms/20210518_150755_b2d44@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/arm64/b/backport-iwlwifi-dkms/20210518_151028_db879@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/ppc64el/b/backport-iwlwifi-dkms/20210518_133640_db879@/log.gz ** Affects: backport-iwlwifi-dkms (Ubuntu) Importance: Undecided Status: New ** Affects: linux-unstable (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929180 Title: backport-iwlwifi-dkms/8613-0ubuntu2 ADT test failure with linux- unstable/5.13.0-3.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1929180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929181] Re: backport-iwlwifi-dkms/8613-0ubuntu2 ADT test failure with linux-unstable/5.13.0-3.3
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1929181/+attachment/5499185/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929181 Title: backport-iwlwifi-dkms/8613-0ubuntu2 ADT test failure with linux- unstable/5.13.0-3.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1929181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929181] [NEW] backport-iwlwifi-dkms/8613-0ubuntu2 ADT test failure with linux-unstable/5.13.0-3.3
Public bug reported: This is a scripted bug report about ADT failures while running backport- iwlwifi-dkms tests for linux-unstable/5.13.0-3.3 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/amd64/b/backport-iwlwifi-dkms/20210518_150755_b2d44@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/arm64/b/backport-iwlwifi-dkms/20210518_151028_db879@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/ppc64el/b/backport-iwlwifi-dkms/20210518_133640_db879@/log.gz ** Affects: backport-iwlwifi-dkms (Ubuntu) Importance: Undecided Status: New ** Affects: linux-unstable (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929181 Title: backport-iwlwifi-dkms/8613-0ubuntu2 ADT test failure with linux- unstable/5.13.0-3.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1929181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
** Attachment added: "lspci-5.13.0-051300rc2.after.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5499184/+files/lspci-5.13.0-051300rc2.after.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
@Koba, I have attached output from "sudo lspci -vvv" before and after suspend/resume for kernel 5.13.0-051300rc2-generic. ** Attachment added: "lspci-5.13.0-051300rc2.before.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5499183/+files/lspci-5.13.0-051300rc2.before.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
In case it helps narrow down where to look for the issue, I have dropped back to the stock 5.8 kernel from the linux-image-5.8.0-53-generic package in 21.04. With the 5.11 (from the standard repositories) and the 5.12 and 5.13rc2 (from mainline) I couldn't manage a day without a lock up. Usually it was between 2 and 6, but with the 5.8 I have been without problems for over a day now. I have had issues on the 5.8 series before, but nowhere near as much as the newer kernels. I suspect, not being a kernel developer, that the issue may be somewhere in the changes post 5.8. Mentioning in the hope that some extra info is of use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928600 Title: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929158] Re: upgrade of libvpx6 crashes ffmpeg
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1929158/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929158 Title: upgrade of libvpx6 crashes ffmpeg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1929158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898928] Re: package ubuntu-advantage-tools 19.6~ubuntu14.04.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
I see the same issue: DistroRelease: Linux Mint 19 Tara Setting up ubuntu-advantage-tools (27.0.2~18.04.1) ... /var/lib/dpkg/info/ubuntu-advantage-tools.postinst: 5: .: Can't open /etc/os-release dpkg: error processing package ubuntu-advantage-tools (--configure): installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: ubuntu-advantage-tools E: Sub-process /usr/bin/dpkg returned an error code (1) And to answer Andreas, there is no /etc/os-release on my system: $ ls -la /etc/os-release ls: cannot access '/etc/os-release': No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898928 Title: package ubuntu-advantage-tools 19.6~ubuntu14.04.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1898928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922089] Fix proposed to neutron (stable/wallaby)
Fix proposed to branch: stable/wallaby Review: https://review.opendev.org/c/openstack/neutron/+/792538 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922089 Title: [ovn] enable_snat cannot be disabled once enabled To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1922089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922089] Fix proposed to neutron (stable/victoria)
Fix proposed to branch: stable/victoria Review: https://review.opendev.org/c/openstack/neutron/+/792537 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922089 Title: [ovn] enable_snat cannot be disabled once enabled To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1922089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922089] Fix proposed to neutron (stable/ussuri)
Fix proposed to branch: stable/ussuri Review: https://review.opendev.org/c/openstack/neutron/+/792536 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922089 Title: [ovn] enable_snat cannot be disabled once enabled To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1922089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926792] Re: Fix kernel panic at boot on dual GFX systems
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926792 Title: Fix kernel panic at boot on dual GFX systems To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926100] Re: Hotspot (access point) is not working properly on two different wifi adapters.
Can you please attach output of `iw list`, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926100 Title: Hotspot (access point) is not working properly on two different wifi adapters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925675] Re: hirsuit kernel fails to detect monitor plugged into USBC thunderbolt socket
Sure, thanks for the update. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925675 Title: hirsuit kernel fails to detect monitor plugged into USBC thunderbolt socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925675] Re: hirsuit kernel fails to detect monitor plugged into USBC thunderbolt socket
Annoyingly, I have to report that this morning the display in question worked fine with both the latest stable hirsuit kernel (5.11.0-17-generic) and the version I reported the bug for (5.11.0-16-generic). If I can find a way to reproduce it reliably, then I'll re-open this bug, but for the moment, maybe close as non-reproducible? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925675 Title: hirsuit kernel fails to detect monitor plugged into USBC thunderbolt socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929155] Re: i cant upgrade from 18.04 to 20.04.02 "Cannot calculate the upgrade"
Thank you for taking the time to report this issue and helping to make Ubuntu better. The error message you obtained says "* Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again." If you check your sources, you have 3rd party packages installed, a 3rd party MATE PPA & https://deb.nodesource.com/node_14.x which provides the package that is at least one of your issues (ie. nodejs 14.17.0-1nodesource1 I would recommend following the advice in the error message provided in your bug description. I've marked this incomplete, as you haven't followed the instructions of the error message; or remove all 3rd party software before allowing upgrade to proceed. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929155 Title: i cant upgrade from 18.04 to 20.04.02 "Cannot calculate the upgrade" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1929155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929155] Re: i cant upgrade from 18.04 to 20.04.02 "Cannot calculate the upgrade"
You can find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 (I intended adding this sorry) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929155 Title: i cant upgrade from 18.04 to 20.04.02 "Cannot calculate the upgrade" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1929155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: HIrsute live session takes ages to boot on BIOS systems
Hi, Michael Hudson-Doyle wrote: > I'm going to > subscribe Thomas Schmitt, xorriso upstream, who knows enormously more than > I do about all this stuff. Well, firmware can always outsmart any preparation in an ISO. My personal expertise is restricted to ISO 9660 and ends when firmware found the bootloader in the ISO image. When the machine can complain about "grub" then the firmware obviously found such an entry point and ran some GRUB equipment. Naive guess: Can the problem here be related to the switch from ISOLINUX to GRUB for legacy BIOS booting ? (Ubuntu 19.04 has ISOLINUX, 20.10 has GRUB in the MBR.) The fact that it works better after conversion from GPT to MBR partition table could be explained that GRUB wants some more of its components when having been booted from a medium with valid GPT. I write "wants", because it finally is able to boot without it, possibly after a long timeout. The complained "grub_platform" is documented to be a variable which is promised to be set by GRUB "normal" mode. https://www.gnu.org/software/grub/manual/grub/html_node/grub_005fplatform.html So i wonder whether the BIOS MBR of GRUB and its subsequent boot stages do not set grub_platform because they are not in "normal" mode ? Maybe grub-devel mailing list can give hints about MBR boot code, normal mode, and the grub_platform variable. -- Whatever, here is a summary of recent efforts to make all x86 firmwares recognize one of the offered entry points: The youngest attempt to get it right for all existing machines was https://bbs.archlinux.org/viewtopic.php?id=264096 where in the end a slightly improved variation of the Fedora layout by Matthew J. Garrett seems to have done the trick. The layout by mjg was used by Ubuntu up to october 2020 and is still used by Debian and Fedora. Last year Ubuntu for a short time moved to a neat MBR partition table layout, but then had to switch to GPT, because some EFIs did not recognize the MBR-only ISO: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148 But that neat GPT did not work for some old HP machines. So a small deviation from the GPT specs was added in form of an extra MBR partition of type 0x00 which carries the "bootable" flag: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308 The archlinux thread above started about an ISO with that layout. But it was discovered that Lenovo Thinkpad T420 did not work with it in legacy BIOS mode (CSM). It did well with EFI. The solution was to go back to mjg layout with the improvement that the EFI partition ins not inside the ISO 9660 partition any more (i.e. it is not a data file in the ISO 9660 filesystem). The result is still not as neat as Ubuntu's current partition layout. I suspect that nearly 10 years of mjg layout in Fedora, Ubuntu, and Debian spoiled the firmware programmers who made sure that this weird jackalope is recognized by their EFI. To my theory the mistake sneaked in that some firmwares decide that there is no EFI equipment if there is no GPT (valid or not) whereas some decide there is no BIOS equipment if there is a valid GPT. Additionally there is the old mistake of some BIOS-only machines to ignore the MBR boot code if there is no MBR partition with "bootable" flag. But as said above: If it can say "grub" then the problem happens after successful recognition of the boot entry point. -- Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: HIrsute live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929138] Re: build fails due to relative paths in Makefile.am using automake before version 1.16.1
Fix sent to fwts-devel for review: https://lists.ubuntu.com/archives /fwts-devel/2021-May/013077.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929138 Title: build fails due to relative paths in Makefile.am using automake before version 1.16.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1929138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926806] Re: pipx terminates with "TypeError: __init__() got an unexpected keyword argument 'encoding'"
** Changed in: python-pipx (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: python-pipx (Ubuntu Hirsute)
Status: New => In Progress
** Description changed:
SRU: Backport pipx version compatible with Python 3.9
Let's backport the version from impish to hirsute.
Regression potential: None, because the version in 21.04 doesn't work at
- all.
+ all, and there are no dependencies or build dependencies.
Tests: The package builds, and passes its tests. a simple
- pipx install pycowsay
+ pipx install pycowsay
works
Running `pipx` with any parameters except for help results in the
following error:
pipx uninstall-all
Traceback (most recent call last):
File "/usr/bin/pipx", line 11, in
load_entry_point('pipx==0.12.3.1', 'console_scripts', 'pipx')()
File "/usr/lib/python3/dist-packages/pipx/main.py", line 496, in cli
exit(run_pipx_command(parsed_pipx_args, binary_args))
File "/usr/lib/python3/dist-packages/pipx/main.py", line 191, in
run_pipx_command
commands.uninstall_all(PIPX_LOCAL_VENVS, LOCAL_BIN_DIR, verbose)
File "/usr/lib/python3/dist-packages/pipx/commands.py", line 432, in
uninstall_all
uninstall(venv_dir, package, local_bin_dir, verbose)
File "/usr/lib/python3/dist-packages/pipx/commands.py", line 409, in
uninstall
metadata = venv.get_venv_metadata_for_package(package)
File "/usr/lib/python3/dist-packages/pipx/Venv.py", line 65, in
get_venv_metadata_for_package
data = json.loads(
File "/usr/lib/python3.9/json/__init__.py", line 359, in loads
return cls(**kw).decode(s)
TypeError: __init__() got an unexpected keyword argument 'encoding'
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: Ubuntu 21.04
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: pipx 0.12.3.1-3ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.11.0-16.17-lowlatency 5.11.12
Tags: hirsute
Uname: Linux 5.11.0-16-lowlatency x86_64
UpgradeStatus: Upgraded to hirsute on 2020-12-28 (123 days ago)
UserGroups: adm audio cdrom dip docker floppy netdev plugdev scanner sudo sys
systemd-journal tty video wireshark
_MarkForUpload: True
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926806
Title:
pipx terminates with "TypeError: __init__() got an unexpected keyword
argument 'encoding'"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pipx/+bug/1926806/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
Would be very nice if it will be available in 20.04 ubuntu. Very annoying issue :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880405 Title: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Stephane, I can't reproduce the hang on my test machine with gdb. (Despite your investigation seems right for me). CPU usage stay low, as usual on this machine (same slapd config than the production servers, but only 1 CPU is available). To prove I made the right steps :-) : $ gdb --args ldapsearch ldaps://front -x [...] (gdb) break write Function "write" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (write) pending. (gdb) run Starting program: /usr/bin/ldapsearch ldaps://front -x conti [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Breakpoint 1, __GI___libc_write (fd=3, buf=0x5578b2f0, nbytes=14) at ../sysdeps/unix/sysv/linux/write.c:27 27 ../sysdeps/unix/sysv/linux/write.c: No such file or directory. (gdb) continue Continuing. Breakpoint 1, __GI___libc_write (fd=1, buf=0x5578b2f0, nbytes=16) at ../sysdeps/unix/sysv/linux/write.c:27 27 in ../sysdeps/unix/sysv/linux/write.c Another information (maybe not important, or not related to this case): since monday, I started to migrate LDAP DB backend from BDB to LMDB. So I must wait next slapd hang to be sure DB change have no impact on this issue. (in the past there were sometimes 2 or 3 weeks elapsed between two slap hang). note: I reverted DB backend on my test machine but without reproducing the issue too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929166] Re: TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station
** Description changed: + [SRU Justification] + [Impact] The NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. Then display managed by the NVDIA GPU shows nothing until system reboot. Note that it only happens when NVIDIA GPU in either Performance mode or On-Demand mode. [Fix] A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to do source clock control of the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-NVWakeup". No other platforms will be affected. ** Summary changed: - TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station + TGL-H system NV GPU fallen off the bus after resuming from s2idle with the external display connected via docking station -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929166 Title: TGL-H system NV GPU fallen off the bus after resuming from s2idle with the external display connected via docking station To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926806] Re: pipx terminates with "TypeError: __init__() got an unexpected keyword argument 'encoding'"
** Description changed:
+ SRU: Backport pipx version compatible with Python 3.9
+
+ Let's backport the version from impish to hirsute.
+
+ Regression potential: None, because the version in 21.04 doesn't work at
+ all.
+
+ Tests: The package builds, and passes its tests. a simple
+ pipx install pycowsay
+ works
+
+
+
Running `pipx` with any parameters except for help results in the
following error:
pipx uninstall-all
Traceback (most recent call last):
- File "/usr/bin/pipx", line 11, in
- load_entry_point('pipx==0.12.3.1', 'console_scripts', 'pipx')()
- File "/usr/lib/python3/dist-packages/pipx/main.py", line 496, in cli
- exit(run_pipx_command(parsed_pipx_args, binary_args))
- File "/usr/lib/python3/dist-packages/pipx/main.py", line 191, in
run_pipx_command
- commands.uninstall_all(PIPX_LOCAL_VENVS, LOCAL_BIN_DIR, verbose)
- File "/usr/lib/python3/dist-packages/pipx/commands.py", line 432, in
uninstall_all
- uninstall(venv_dir, package, local_bin_dir, verbose)
- File "/usr/lib/python3/dist-packages/pipx/commands.py", line 409, in
uninstall
- metadata = venv.get_venv_metadata_for_package(package)
- File "/usr/lib/python3/dist-packages/pipx/Venv.py", line 65, in
get_venv_metadata_for_package
- data = json.loads(
- File "/usr/lib/python3.9/json/__init__.py", line 359, in loads
- return cls(**kw).decode(s)
+ File "/usr/bin/pipx", line 11, in
+ load_entry_point('pipx==0.12.3.1', 'console_scripts', 'pipx')()
+ File "/usr/lib/python3/dist-packages/pipx/main.py", line 496, in cli
+ exit(run_pipx_command(parsed_pipx_args, binary_args))
+ File "/usr/lib/python3/dist-packages/pipx/main.py", line 191, in
run_pipx_command
+ commands.uninstall_all(PIPX_LOCAL_VENVS, LOCAL_BIN_DIR, verbose)
+ File "/usr/lib/python3/dist-packages/pipx/commands.py", line 432, in
uninstall_all
+ uninstall(venv_dir, package, local_bin_dir, verbose)
+ File "/usr/lib/python3/dist-packages/pipx/commands.py", line 409, in
uninstall
+ metadata = venv.get_venv_metadata_for_package(package)
+ File "/usr/lib/python3/dist-packages/pipx/Venv.py", line 65, in
get_venv_metadata_for_package
+ data = json.loads(
+ File "/usr/lib/python3.9/json/__init__.py", line 359, in loads
+ return cls(**kw).decode(s)
TypeError: __init__() got an unexpected keyword argument 'encoding'
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: Ubuntu 21.04
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: pipx 0.12.3.1-3ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.11.0-16.17-lowlatency 5.11.12
Tags: hirsute
Uname: Linux 5.11.0-16-lowlatency x86_64
UpgradeStatus: Upgraded to hirsute on 2020-12-28 (123 days ago)
UserGroups: adm audio cdrom dip docker floppy netdev plugdev scanner sudo sys
systemd-journal tty video wireshark
_MarkForUpload: True
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926806
Title:
pipx terminates with "TypeError: __init__() got an unexpected keyword
argument 'encoding'"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pipx/+bug/1926806/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928441] Re: Fail in upgrade to 21.04
/var/log/dist-upgrade/apt.log file : https://drop.infini.fr/r/C7X0J6JTqr#Iy6UBAya4aJ4GOX/k3xszribWC3dS7LrQZOa4MKlN9Q= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928441 Title: Fail in upgrade to 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1928441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928441] Re: Fail in upgrade to 21.04
Thanks. Added as a comment ! https://drop.infini.fr/r/C7X0J6JTqr#Iy6UBAya4aJ4GOX/k3xszribWC3dS7LrQZOa4MKlN9Q= On 21/05/2021 01:15, Brian Murray wrote: > /var/log/dist-upgrade/apt.log file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928441 Title: Fail in upgrade to 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1928441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
@Henrik, would you please help to collect lspci -vvv #sudo lspci -vvv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929139] Re: control center taking over!
** Tags added: rpi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929139 Title: control center taking over! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1929139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929144] Re: linux ADT test failure with linux/4.15.0-144.148 i386 (stress-misaligned.0 failed)
My bad, I fat fingered an #endif Fix committed: https://kernel.ubuntu.com/git/cking/stress-ng.git/commit/?id=231800be6f0812821318a39addce91181c4c9068 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929144 Title: linux ADT test failure with linux/4.15.0-144.148 i386 (stress- misaligned.0 failed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929166] Re: TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station
** Description changed: [Impact] The NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. Then display managed by the NVDIA GPU shows nothing until system reboot. Note that it only happens when NVIDIA GPU in either Performance mode or On-Demand mode. [Fix] - A BIOS workaround is used to skip the ACPI method PGSC which invokes IPSC to power on the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. + A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to power on the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. - [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-NVWakeup". No other platforms will be affected. ** Description changed: [Impact] The NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. Then display managed by the NVDIA GPU shows nothing until system reboot. Note that it only happens when NVIDIA GPU in either Performance mode or On-Demand mode. [Fix] - A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to power on the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. + A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to power on/off the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-NVWakeup". No other platforms will be affected. ** Description changed: [Impact] The NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. Then display managed by the NVDIA GPU shows nothing until system reboot. Note that it only happens when NVIDIA GPU in either Performance mode or On-Demand mode. [Fix] - A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to power on/off the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. + A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to do source clock control of the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-NVWakeup". No other platforms will be affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929166 Title: TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station To manage notifications about this bug go to:
[Bug 1926806] Re: pipx terminates with "TypeError: __init__() got an unexpected keyword argument 'encoding'"
** Also affects: python-pipx (Ubuntu Hirsute) 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/1926806 Title: pipx terminates with "TypeError: __init__() got an unexpected keyword argument 'encoding'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pipx/+bug/1926806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15
Retested with the following instances, test passed as expected: bionic-linux-aws-aws-amd64-4.15.0-t2.small-ubuntu_ltp bionic-linux-aws-fips-aws-fips-amd64-4.15.0-t2.small-ubuntu_ltp https://github.com/linux-test- project/ltp/commit/9dcbf4e96a41ac69842e705d4dea51fc8e7b0860 Thank you! ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854722 Title: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929166] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1929166 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929166 Title: TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929166] Re: TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station
** Tags added: oem-priority originate-from-1925291 somerville ** Tags added: originate-from-1923729 ** Tags added: originate-from-1923722 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929166 Title: TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929166] [NEW] TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station
Public bug reported: [Impact] The NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. Then display managed by the NVDIA GPU shows nothing until system reboot. Note that it only happens when NVIDIA GPU in either Performance mode or On-Demand mode. [Fix] A BIOS workaround is used to skip the ACPI method PGSC which invokes IPSC to power on the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-NVWakeup". No other platforms will be affected. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: Chris Chiu (mschiu77) Status: In Progress ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => Chris Chiu (mschiu77) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929166 Title: TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927764] Re: Please backport debhelper 13 to bionic and focal
** Also affects: debhelper (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/1927764 Title: Please backport debhelper 13 to bionic and focal To manage notifications about this bug go to: https://bugs.launchpad.net/bionic-backports/+bug/1927764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929013] Re: upgrade of server from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS fail
Thank you for your fast answer. The new version of the release upgrader solved my issue. The only point which I considered after upgrade was that mysql-server-5.7 was removed but mysql-server-8.0 was not installed. I fixed this manually by installing the mysql-server-8.0 from the command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929013 Title: upgrade of server from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1929013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884274] Re: After login, plasma takes extremely long before desktop is shown
Looks like I may have this problem as well. Everything is perfect until login then it hangs without the desktop appearing (no, I haven't waited 20mins :)). At first I thought it was yakuaki causing it as that would autostart with nothing else but having uninstalled that yesterday it is actually worse now. Today I had to hard restart three times to get to the desktop. I am unable to switch to a different session (ctrl + alt + f2). Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-73-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8300H CPU @ 2.30GHz Memory: 7.5 GiB of RAM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884274 Title: After login, plasma takes extremely long before desktop is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1884274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
** Changed in: linux-oem-5.10 (Ubuntu Focal) 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/1928242 Title: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1928242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
For me this happens only when I'm using Blender (2.92 installed via snap) and when my system is busy (CPU usage is more than 70%) but because I'm mainly working with blender on my machine that's why this bug has affected me severely. Before starting my new project (that I'm currently working on) I never had experienced this before while ordinary PC usage (browsing web and etc). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928750] Re: Support mic-mute on Dell's platform
** Changed in: linux-oem-5.10 (Ubuntu Focal) 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/1928750 Title: Support mic-mute on Dell's platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1928750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909814] Re: Keyboard not working
Latest kernel not working for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
