• 29 Posts
  • 325 Comments
Joined 1 年前
cake
Cake day: 2025年4月2日

help-circle








  • All in all you ended up at the whole point I was making, but somehow you first had to claim that it’s all nonsense.

    No, I pointed out that the problem you described is completely avoidable, which wasn’t apparent in your original comment. This is an important distinction to other readers who are considering a move to Linux, since they otherwise might be put off by your suggestion that doing so is necessarily a hardware lottery.

    It was a different perspective, not a personal attack.

    Your combative, snarky response is unpleasant, unwarranted, and unnecessary. Goodbye.




  • taking care that they only select components that work fine under Windows is a big part of why there isn’t a hardware lottery under Windows.

    There isn’t a hardware lottery under Linux, either, unless you buy random hardware instead of choosing known-good components or turning to one of the system vendors who do this for you.

    I find it kind of weird that people who would never take mystery medication without it being prescribed to them, and would never buy a paycheck worth of food without considering its contents against their allergies and tastes, would buy a computer without checking whether it will run the software they intend to use.

    Perhaps the perceived problem would fade if we taught people that computers and operating systems are not all equal, and that just as MacOS is more likely to run on a machine made for it, Linux is more likely to run on a machine made for it. (Edit: The same is true for Windows, for what it’s worth.)





  • The go env -w command can make most go environment variable settings persistent for the current user. Alternatively, you could set the environment variable in your shell’s login script.

    Be sure to read go’s docs for individual environment variables, because go doesn’t respect all methods of setting them in every case. (For example, it ignores certain approaches to disabling its telemetry. How convenient for Google.)





  • Time for the usual troubleshooting steps:

    • Have you Checked for errors in the log output of…
    • What changed on your system between the last time WoW worked properly and the first time it didn’t?
      • OS update?
        • Kernel?
        • Drivers?
      • Proton update?
      • Steam update?
      • Game update?
      • Battle.net update?
    • Are you watching for other people discussing the same problem?

    Blizzard has a recurring history of making changes to Games and Battle.net that break in Wine. When this happens, workarounds can sometimes be found (such as reverting to a prior Battle.net version), but a real fix often requires waiting a few weeks or months for Proton to adapt. It happened roughly once per year when I was last playing their games.

    Good luck.