© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
For me, it's really f, on my "Jammy" (KDE Neon).
5.19.0-42 - no boot
And because of really stupid decision to, by default hide Grub and disable os prober, it basically broke my system. (For whatever reason shortcut for grub is also not working.) I had to unplug SATA drive, boot from live, replug the drive, mount with bind, chroot, change the grub setting, update-grub, and reboot with the grub boot menu, and guess what 5.19.0-42 still unbootable. Systemd gets stuck in random moments.
I also tried 5.19.0-42 recovery and it might have worked, but I am not sure, because it refused to work with my normal keyboard and only accepted my custom keyboard that has only arrows, ESC, and enter. That was enough to get me out of the recovery menu but not through the login screen. It's f anyway.
Thx @koba for trying, but again no HDMI audio for me. At least you are someone who wants to fix it, thx.
-------
Now rant about Ubuntu.
I am getting very frustrated. Whenever my GPU kicks in my onboard audio sound like 1000 daemons eating the souls of innocent in the abyss. Ubuntu, wth? I get that bugs happen, but this has been fixed a month ago and this kind of situation is what makes Linux shit in the eyes of newbies. Breaking HDMI audio would be unacceptable on Windows or MAC.