I just ran into this bug also on Ubuntu 20 LTS after updating the kernel a week ago (multiboot laptop with Ubuntu and Windows 10). After figuring out that it's not a hardware issue (since windows still booted normally), I made the switch to Jammy, installed Ubuntu and all my software from scratch, and it worked during the first boot cycle. Rebooting a week later after living on standby, I am screwed again. Why is this neither fixed nor is there a set of instructions how to deal with it for the time being, if it is HIGH priority? Could you please provide simple, pedestrian instructions (including full paths, etc.) for a user who is used to working in bash, but not to the technical details of the inner workings of Ubuntu. I need a robust workaround until this bug is eventually fixed, and have a hard time believing that the bug still shows after the last post is 4 weeks old. Any help is appreciated.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
