Comment 4 for bug 1977875

Sorry, just saw the e-mail notifications of the last two posts.

You will note if you read the bug report that the problem is a boot hang. No means exists to run any commands whatsoever, including journalctl.

Besides, the machine is long gone. I've probably installed and wiped Ubuntu 22.04 (chiefly Desktop but also Server) several dozens of times over a period of weeks. I haven't been too sentimental about retaining failed software.

I've given you enough breadcrumbs to both (a) lead you to the problem (which should be evident from the previously-attached dependency tree and other files) and (b) configure a machine to reproduce it. In fact, I would expect the dependency tree would be largely tantamount to what the logs would reveal.

My focus is on getting a production machine running, which has yet to occur, nearly three months after release. I really need to get back to my own business. If I have a few hours if ever Ubuntu 22.04 installs, I'll see about re-creating the problem. This has put my business back three months so far, and I have a lot of catch-up, so don't hold your breath. You're probably better off reading the attached files and recreating the failure on your end.