Had this specific issue a couple days ago, but, to make it worse, the up-to-date package was not yet available. So discord would straight up not start at all.
So, to add another tip: telling discord to shut up about updates is the only reasonable response to that bs in my opinion. I’ll update when I want to, thank you very much.
Just add "SKIP_HOST_UPDATE":true in the settings file at ~/.config/discord/settings.json to put this software in its place.
Yeah Discord has been wacky on Linux lately, they pushed maybe 4 different updates the past week that forced you to update the package immediately.
Pro tip: Sync the package manager database before trying to update. It could tell you there are no updates when it’s just pacman being out of date.
Had this specific issue a couple days ago, but, to make it worse, the up-to-date package was not yet available. So discord would straight up not start at all.
So, to add another tip: telling discord to shut up about updates is the only reasonable response to that bs in my opinion. I’ll update when I want to, thank you very much. Just add
"SKIP_HOST_UPDATE": truein the settings file at~/.config/discord/settings.jsonto put this software in its place.sometimes i use this one too
this is one of the fixes the manual i cited suggests, legit fix
Partial upgrades are unsupported on Arch Linux.
Huh, I’ve done it a couple of times with no issue. Updated the above comment to remove that recommendation, then.
Unsupported doesn’t mean it don’t work.
Iv done partial upgrades for years and never broken anything. But if something did break i would be entirely on my own to fix shit