[Bug 1958718] [NEW] Crash on wake with kernel version 5.13
Public bug reported: With "linux-image-5.13.0-27-generic" on Ubuntu 20.04.3 LTS, my notebook (Thinkpad T14) crashes when waking up after being suspended. The screen displays what I would describe as "colourful snow" with some vertical stripes on the right edge of the display. The only thing I can do is power off the machine by holding the power button for several seconds and then restart. With "linux-image-5.11.0-46-generic", this does not happen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 16:05:18 2022 InstallationDate: Installed on 2020-12-28 (389 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958718 Title: Crash on wake with kernel version 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761895] Re: Post-install boot loop: "System BootOrder not found."
I found the reason for this problem: it turned out to be the BIOS setting "Boot Order Lock". After disabling it, I saw the above message one more time, then Ubuntu started properly (and a new boot entry called "ubuntu" appeared in the BIOS). I don't know if this is possible, but it would be a good idea to detect that the "ubuntu" boot entry wasn't actually created and display an error message. If it's not possible, an additional hint about "Boot Order Lock" or similar BIOS settings might be helpful (as well as showing the message for more than a split-second). ** Package changed: ubiquity (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761895 Title: Post-install boot loop: "System BootOrder not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1761895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761895] [NEW] Post-install boot loop: "System BootOrder not found."
Public bug reported: Bionic Beaver Final Beta doesn't install properly on my computer (Thinkpad E480 with an NVMe SSD, no SATA disk). After finishing the installation, the machine repeatedly shows these messages and reboots: System BootOrder not found. Initializing defaults. Creating boot entry "Boot" with label "ubuntu" for file "\EFI\ubuntu\shimx64.efi" Reset System This happens both with automatic and manual partitioning. Setting the "UEFI/Legacy" switch in the BIOS to "Both" or "UEFI Only" also doesn't make a difference. (The installer doesn't boot at all when choosing "Legacy Only".) I checked the EFI partition and the file "\EFI\ubuntu\shimx64.efi" does exist. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761895 Title: Post-install boot loop: "System BootOrder not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1761895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452006] Re: Gajim freezes whole system on start
The bug linked by unrud (#5) seems to describe the cause (at least in my case). I was able to make Gajim start without freezing the system by removing read access to the /proc file: sudo chmod o-r /proc/brcm_monitor0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452006 Title: Gajim freezes whole system on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gajim/+bug/1452006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452006] Re: Gajim freezes whole system on start
I'm encountering this on Ubuntu 16.04.1 with the default Gajim package. If there is information that could be helpful for the investigation, please tell me how to save it before the whole system crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452006 Title: Gajim freezes whole system on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gajim/+bug/1452006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234920] Re: Mismatching UUIDs after Hardy server install
Sorry, I'm not planning to re-install my server (or something comparable) in the near future. Hopefully some of the other commenters can contribute information. I have since moved to a non-mirrored config for /boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/234920 Title: Mismatching UUIDs after Hardy server install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/234920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Correct my if I'm wrong, but it looks like the patch file is not actually in /usr/share/initramfs-tools/scripts? If you downloaded the file to any other location, you need to specify the full path when executing patch. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Correct my if I'm wrong, but it looks like the patch file is not actually in /usr/share/initramfs-tools/scripts? If you downloaded the file to any other location, you need to specify the full path when executing patch. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
I have created a patch for the initramfs-tools script as suggested by Ken in this comment: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/120375/comments/47 In order to apply it (as root), cd /usr/share/initramfs-tools/scripts, patch initramfs-mdadm-assemble-scan.patch, then update-initramfs -u. With an initrd patched in this manner, I was able to disconnect either of my harddrives and still boot my server without manual intervention. The patch does not address the generous wait for the missing harddrive, so give it some time. ** Attachment added: Patch for initramfs-tools as suggested by Ken on 2008-03-31 http://launchpadlibrarian.net/15929571/initramfs-mdadm-assemble-scan.patch -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
I have created a patch for the initramfs-tools script as suggested by Ken in this comment: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/120375/comments/47 In order to apply it (as root), cd /usr/share/initramfs-tools/scripts, patch initramfs-mdadm-assemble-scan.patch, then update-initramfs -u. With an initrd patched in this manner, I was able to disconnect either of my harddrives and still boot my server without manual intervention. The patch does not address the generous wait for the missing harddrive, so give it some time. ** Attachment added: Patch for initramfs-tools as suggested by Ken on 2008-03-31 http://launchpadlibrarian.net/15929571/initramfs-mdadm-assemble-scan.patch -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Excellent, thanks! -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234786] Re: dovecot-auth: pam_smbpass(dovecot:auth): unrecognized option [missingok]
I am seeing this error message very often too, when using sudo. It seems to be caused by the missingok parameter on the pam_smbpass line in /etc/pam.d/common-auth, which prevents excessive error logging when pam_smbpass isn't installed, but in turn causes the module to complain about this unknown parameter when it *is* installed. The appropriate component for this bug is not dovecot, but libpam-smbpass doesn't exist either. -- dovecot-auth: pam_smbpass(dovecot:auth): unrecognized option [missingok] https://bugs.launchpad.net/bugs/234786 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 234786] Re: dovecot-auth: pam_smbpass(dovecot:auth): unrecognized option [missingok]
I am seeing this error message very often too, when using sudo. It seems to be caused by the missingok parameter on the pam_smbpass line in /etc/pam.d/common-auth, which prevents excessive error logging when pam_smbpass isn't installed, but in turn causes the module to complain about this unknown parameter when it *is* installed. The appropriate component for this bug is not dovecot, but libpam-smbpass doesn't exist either. -- dovecot-auth: pam_smbpass(dovecot:auth): unrecognized option [missingok] https://bugs.launchpad.net/bugs/234786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Many thanks to everyone working on this! I tried Ken's solution and it worked with either disk attached. I have a lot more confidence putting my server into production now. :) -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
