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
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
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
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,
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
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,
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
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
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
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
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
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
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
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
14 matches
Mail list logo
