PDF reference of the API here: https://cdn.arstechnica.net/wp-content/uploads/2026/01/2025.12.18-SoundTouch-Web-API.pdf

Honestly don’t know why people are up in arms and even posting about it. They aren’t saying they are removing the capability, just the default. Big whoop.

Depends on when you deleted it and how much activity time on that drive has passed. If it’s just an ext4 drive and you haven’t had a large number of changes to that partition since it’s been deleted, some different recovery tools may find it.

Photorec is pretty capable though, so if it’s not finding it, that’s probably the end of that.

1. Boot into a LiveUSB of the same version of distro you tried to install
2. View the drive mappings to see what they are detected as
3. Ensure your newly created partitions can mount correctly
4. Check /etc/fstab on your root drive (not the LveUSB filesystem) to ensure they match as the ones detected while in LiveUSB
5. Try rebooting

Report changes here.

Dude…I’m not even eating my time with y’all who have zero clue as to how QA/CI/UAT works. It’s such a waste of time.

Steam/Proton is only tested for KDE/GNOME, and that’s it. Hands down. Not even up for fucking debate. It’s a FACT.

You can read the docs, repos, GitHub Issues, forums, and everything else you want. That’s the facts, and it’s not going to change. Just because it’s OSS doesn’t mean they have all the time in the world to make sure your edge cases work FFS.

deleted by creator

deleted by creator

If you’re using a custom WM, your experience is going to vary WRT to Steam/Proton being able to run properly.

Project looks dead, and last commit was 2 years ago. Probably just some incompatible difference between a modern build and whenever the last work was done on it.

Read the real docs and repo though, not just somebody’s post about it: https://github.com/ReimuNotMoe/ydotool

OHHH…you didn’t get an actual on screen prompt, you just decided to reinstall. My bad.

Wait…wha?

What prompted you to reinstall your ENTIRE OS? That should almost never be necessary under any circumstances.

Because those are different codebases packaged differently and need access to different things in your environment.

If the developer has a public GitHub, feel free to notify them, but this is likely not treated as a bug since it’s an issue with Flatpak and your permissions. If you run the project bare and it has this same issue, then it’s still an environment issue it seems. Probably not technically a problem with their code explicitly.

If it works, then just install Flatseal and put this an environment variable for the package. Will run without issue from them on.

From the logs it looks more like an issue getting to that dbus socket, which can also be tweaked with Flatseal.

Iris is just the codename of the Intel graphics. This looks more like a permissions issue with Flatpak.

Are you saying this then works fine without problems when you export that module reference?

Cool. So I can get one for my massive Clit as well then? I want everyone to pay respect and marvel at it.

Am engineer. Know zero professional people in the engineering community who use AI browsers, and very few who even touch AI for anything aside from docs or stats.

In my personal life I know zero people who use these browsers. I think this is just panic from the higher ups at Mozilla who have no idea what in the fuck the company should be doing or is about, even.

Start making tools to give to people to combat this bullshit from the EU. Build a USABLE and decentralized chat app that people can actually use FFS. Build something like Proton and ACTUALLY BECOME SELF-SUFFICIENT.

Others have eaten your lunch because of this exact thing. Do better.