A custom pipewire.conf i modified from /usr/share and put in /etc/pipewire. It made Bazzite unbootable. I booted into my Arch Linux partition and managed to jump through the right directory, found the file, deleted it.
It fixed Bazzite.....sorta. it broke it in a different way by making the OS boot as fast as if it was installed on a conventional hard drive. It's on an SSD.
Did you come right? It's sometimes easier to just switch to an older image in grub, then your pipewire.config change should be undone without needing to do anything special
I uhhh.... Didn't do that. I just went into Rescuezilla and restored an image I made.... yesterday. I'll keep that in mind next time I make my Linux install go boom.
should mention they only kneecapped it on chrome-based browsers; Firefox is retaining Manifest V2 even as they add MV3, and their MV3 implementation doesn't have some of the deficiencies Google put in theirs
Vivaldi will keep MV2 as long as they can but I think they intend to basically build uBlock's capabilities in natively so it wouldn't be dependent on an addon