That’s not what I’m saying at all. I’m saying Collaboras implementation is fundamentally unfit for use.

I used to host a CODE server.

It ran like shit, because it works by rendering the viewport on the remote system, not the client. Instead you essentially send every input to the server, wait for it to render the change, and then send that back to the client. Collabora is like using office software through vnc. Except all the time.

The responsiveness is atrocious. Especially if you try to use it over a less than ideal connection.

But it’s just fucking text data. It shouldn’t require the same infrastructure as remote gaming to be usable. It should be able to handle multiple seconds of latency, and just sync back up without the user ever noticing.

But it can’t. Because it RENDERS on the server. Which means the tiniest hiccup in the connection between server and user causes noticable issues.

How dpes that help me add office suite functionality to my nextcloud instance?

Collabora will never be good.

When I learned it’s “just” a libreoffice fork running on a remote server that is then screenshared to your browser…

The input latency and the graphical wierdness when resizing the viewport suddenly made sense.

I still want something better than onlyoffice for my nextcloud instance, but at least it is responsive.

T480

On thinkpads it is in the corner of the screen.

AFAIK the “right” way to do this is use a virtual device for system audio, and have that in turn output to the actual audio interface, so you can keep it maxed out.

But that doesn’t really feel like the ideal solution.

That said I’m probably missing something. EasyEffects is able to process audio in ways that should enable what you’re asking for, I just don’t know how.

Also, if you haven’t already, check out qpwgraph. It’s a virtual patch bay for routing audio around however you want.

Best part, is it’s not an add-on, really. It’s just a GUI for capabilities that pipewire already has.

Sea shanties intensify

Also food delivery.

In Finland, there used to be “pizza-online” which was really just a directory and ordering system for restaurants that already did delivery themselves.

They took a very small comission, as the site didn’t really do anything except connect restaurant and customer (and provide a review platform). For a long time, they didn’t even have an app.

You’d log in, select a restaurant, browse their menu and place an order. The order goes to the restaurant, and after that the site’s job was done.

It was massively succesful. Every hole in-the-wall pizza place was on there. Finding good food was easy and cheap, and the restaurants reached more customers than ever. And the platform including reviews led to competition in not just price, but quality.

Then pizza-online sold to foodora, and they got shut down, and participating restaurant were no longer allowed to deliver themselves, and the cut taken by the platform skyrocketed.

I would add that a slightly better way would be to do it in raid1 mode instead of single mode.

That way you can move the data over by running a balance, instead of by removing the old volume, which would survive the process being interrupted by a reboot or whatever else.

Then after the balance you can remove the old volume and turn the new one back into a single mode volume.

TL;DR

Install an archival version of Bazzite or whatever else that corresponds to a date when you know it worked correctly.

Bazzite in particular makes this fairly easy. They have straight forward instructions on how to roll back to a given version.

If that fixes it, just use that version and don’t update.

If you want to stick with Cachy, you can use the Arch Archive to downgrade your entire system to an earlier date, or just Gamescope.

AND I AM TELLING YOU TO DOWNGRADE THEM SO YOU CAN SEE IF AN EARLIER VERSION WORKS CORRECTLY, INSTEAD OF SWAPPING OUT THE ENTIRE DISTRO

ONLY TO TRY THE EXACT SAME COMPOSITOR AS IF THAT WOULD FIX IT

So instead of that, try earlier versions! Different distros from the same date are obviously likely to be running similar versions of Gamescope or whatever else might be the cause.

No.

We use the word distro because they’re not really a fully separate OS. Just a different preset with either a lot or almost nothing swapped out as compared to the next.

You are so hung up being correct here you’re missing what I’m actually trying to teach you.

You need to be comparing different versions, not distros. Because the same version of the same software is going to have the same problem, no matter what distro you use.

You don’t even know how to access system logs, and you expect to understand enough about this stuff to successfully correct me on why trying a different distro isn’t that helpful for troubleshooting?

Software packages that are different.

No? The same software is the same software, regardless what distro you install it on.

Gamescope running on top of KDE/Plasma in one distro will not be different from Gamescope running on top of KDE/Plasma in another distro.

Distros are just presets. The vast majority have far more similarities than differences.

What makes one distro different from another, is that it might come with gnome instead of KDE, pacman instead of apt, initd instead of systemd, systemd-boot instead of grub.

Or any other litany of alternative packages that do the same things.

But if you use the same software, then there is little difference between one distro and the next. The main difference is going to be that you installed the same code from a different distributor.

That’s literally where the name “distro” comes from.

Yes.

A distro or distribution is just a collection of software packages, and usually a package manager.

The actual software itself is the same. The list can be different, but where the items overlap, they are the same. How up to date they are can vary, but Plasma 6 on Bazzite is the exact same as Plasma 6 on Cachy.

Systemd is the same systemd across arch, ubuntu, mint, endeavour, fedora, and any others that use it.

Is this not obvius?

Changing the distro does not tell you much. Especially as you’re running the exact same program in the exact same DE, you should absolutely expect the same result.

I don’t have the slightest clue how to do anything with snapshots and it’s been months since it began anyway so I wouldn’t even know where to start

Well, if you didn’t create any, you can’t go back to them.

My suggestion is to find the archival ISOs of older versions and try them WITHOUT updating after installing them offline.

Though, if you end up having to install gamescope from the internet, then you’re likely getting the exact same latest version no matter what distro you use.

Hence, maybe just easier to learn how to install older versions of packages on cachy. The Arch archive repo makes that quite doable.

And even if I did know which version caused the problem, I wouldn’t know where to go from there.

You pin the package/system and prevent it from updating so it keeps working for you. And report the bug so it can be fixed.

All of this stuff is a community effort. You can wait for someone else to figure out the problem of course, but the fastest solution is usually to volunteer yourself.

A different distro is not different software. Distros are really just different ways to install the same exact software.

Gamescope on Bazzite is the same as Gamescope on Cachy. Same for Plasma/KDE.

Why would they be different?

Start with googling how to use journalctl, filter it based on time, errors, or specific processes.

Gamescope is the extra tool.

By going back in time to a version that you know worked.

If that doesn’t fix it, then you can be sure the problem is hardware related, because it still happens on the exact same software that used to work.

And if it does work on older software, then you can go forward one update/snapshot at a time, until you find the change that causes the problem.

Different distros still run the same software. Gamescope isn’t going to be different on Cachy vs Bazzite. Why would it be?

What you need to do is compare different points in TIME (older versions), not the same software just installed differently.

Step one for me whenever I run into an issue, is to load up an earlier system snapshot and see if that fixes it.

If it does, it was an update that changed something. If it doesn’t, it’s likely a hardware issue.

Huh.

I never thought of using that feature of btrfs that way. Brilliant.