• 0 Posts
  • 78 Comments
Joined 1 年前
cake
Cake day: 2023年7月21日

help-circle

  • Anecdotal and likely not very helpful, when I was running a laptop with a 2060, I regularly had freezing issues launching steam, that would freeze the entire desktop on whichever I display I launched it on for anywhere from 10 seconds to a minute. The same issue occurred across multiple Linux distros running multiple Nvidia proprietary driver versions.

    I built a desktop with an AMD GPU to solve the problem and it worked. I really wish I could give you something better than that.



  • Oh yeah sure let’s just have two games that are almost identical, split the efforts of the devs into maintaining them both and releasing consistent updates, split the efforts of the server administrators into maintaining them both, and detract from your concurrent player base from our new game to keep our old game on life support.

    Yall are some crybabies. CS:GO was alive for 10 years, CS2 has been out for 1. It took some time to re-work Dust 2 and add it back into the map pool. I miss agency, I miss cache, but those maps are being reworked and added in over time. It’s a long game scenario here. Give it time and enjoy the free to play game that they sunk a shitload of resources into dramatically improving, that they are going to maintain for at least another decade, just like the last game.





  • This is entirely plausible, but I don’t know if it’s there yet. I’ve long since moved to AMD GPUs so I can’t really fiddle and find out. Give the open source drivers some time to mature.

    Until then, you are reasonably safe running Linux with secure boot turned off. I’m no expert on the matter, but I’m not familiar with any ongoing threats to boot loader in Linux distributions. Stick to your official repos to be safest, unverified user maintained sources like AUR and COPR are possibly more likely to harbor security threats, don’t use them if you don’t need to or don’t know what you’re doing. Password your bios and require a password to log in to your operating system. Common sense is a better defense than secure boot.












  • Love it when people speak with authority and are confidently incorrect. Eugenia is right.

    You could potentially use flatseal to grant the flatpak the necessary permissions, and you might find out what those permissions are by looking for other users experiences with the flatpak version.

    Or, you find the .deb file and it installs natively without being sandboxed. OR, you can find a PPA repository for it, load said repository and install your software.

    But those things require learning a little. Linux rewards self starters who can use a search engine and forums. Hope this maybe points you in the right direction.