Eskating cyclist, gamer and enjoyer of anime. Probably an artist. Also I code sometimes, pretty much just to mod titanfall 2 tho.

Introverted, yet I enjoy discussion to a fault.

  • 10 Posts
  • 1.03K Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle

  • Depends a lot on what you do.

    But yeah. It can be a mix of whoring yourself out to google advertising, facebook, instagram, and shudder… tiktok.

    I’ve gotten to know a guy in the same business as me whose been doing it long enough to have the momentum to just sit in his tiny storefront location, and have customers coming in the door by word of mouth, and by just having seen the store at some point years earlier.

    I am so incredibly jealous. But. I’m a little over a year in and I am starting to pick up clients that heard about me from previous clients, and that is happening more and more.





  • 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.



  • Except cigarettes are a state-run monopoly over there.

    The main reason things are going so slowly is that they can’t bring themselves to stop making so much money.

    The same institution that’s supposed to promote the facts about the health-risks of smoking is the one making stupid amounts of money making and selling it.

    If they ever stop, it’ll be because they transition to other nicotine products, are shift to exporting the product to developing countries (which they already are).



  • It’s just a rating. All cells are rated for some given amount of amps, but you can actually exceed that rating in bursts.

    So I’m jokingly pointing out that you can theoretically pull as many watts as you want.

    You can turn a MWh of energy into a GW of power, as long as you compress it into a short enough duration.

    The battery (or any part of the circuit) just won’t survive the event :D





  • 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.