(Linux) Let me keep using an older version of Discord until I'm ready to upgrade
Having Discord lock me out whenever there is a new update available is very inconvenient and frustrating especially for users of rolling release Linux distributions like Arch Linux and openSUSE Tumbleweed. Package managers (at least particularly on Arch Linux) are not fast enough to keep up which can end up leaving users locked out of the desktop client. Even if they were fast enough, it's still very inconvenient for rolling release distribution users because they are forced to upgrade their entire system instead of doing partial updates since that is how a rolling release distribution works. All I'm asking is for a button whenever there is a message box that says "Must be your lucky day, there's a new update!" that says "I'll update later" or something like that and let me continue using Discord with maybe a grace period since it seems that Discord tends to always update itself on Windows and MacOS. It would cause less pain for certain Linux users in the long run.
-
I agree. Very annoying how I have to wait just to message my friends because of an update.
2 -
Same, using a package from the repository and having to wait for the maintainer to update it, or install it manually and have two versions of discord for that short amount of time is very annoying.
3 -
Yea, thats cruel! Discord is installed using Snap on my laptop, but doesn't work, requiring me to update to 0.0.15, but this version IS NOT AVAILABLE in Snap! And it says "must be your lucky day". Are you f serious?
2 -
Yeap, one of those days when nothing works including discord..
1 -
I totally agree. Its just annoying that i have to wait till the package and its dependencies get updated. For example the newer Version get updated but the decencies that are needed not. So I'm locked out if i dont use the browser version :(
1 -
Quick update:
1. Snap version is not maintained by Discord.
2. Discord 0.0.15 is available in Snap, but in the "edge" channel only so far. Type this to update, if you accept the risk it might be broken
snap refresh --channel=latest/edge discord
3. Or just wait for update in stable channel. Maintainers are working on this.
4. While you're waiting, reduce your pain, using Discord from browser.
-2 -
I generally support the idea of the grace period, but for Arch Linux user there is a workaround:
- Use ABS to download package source
- Update the version in PKGBUILD
- Run makepkg
- InstallThis has the advantage of updating the system package so you don't have to maintain two versions of Discord and you don't have to wait for package maintainers to update it. I've personally done it twice now with situation with updates being what it is and will continue to do so whenever I have to.
-2 -
Wish Discord would work with Snapcraft team, and officially support the Snap version. It's already there...
1 -
Please, yes! It's not always convenient or possible to upgrade: there should be some support period between giving an upgrade message and refusing to start up at all.
1 -
Update: discord 0.0.15 is available in beta channel for Snap so far. Type
snap refresh --channel beta discord
to update.
-1 -
Agreed with OP and the other people in the thread. Posting here and upvoting to get this post more attention.
Somewhat annoying to have to run 2 versions of Linux until i'm ready to ugrade.0 -
The ArchWiki has a section about this: Discord asks for an update not yet available in the repository | Discord | ArchWiki
It recommends adding the following line to the file
~/.config/discord/settings.json:"SKIP_HOST_UPDATE": trueThe full file could then, e.g., look like this:
{ "OPEN_ON_STARTUP": false, "MINIMIZE_TO_TRAY": false, "IS_MAXIMIZED": true, "IS_MINIMIZED": false, "WINDOW_BOUNDS": { "x": 178, "y": 218, "width": 1280, "height": 720 }, "SKIP_HOST_UPDATE": true }To edit the file, you can either open a terminal and use a command like
nano ~/.config/discord/settings.json, or you open your home folder in the normal file explorer, show hidden files (Ctrl+H often does the trick) and then click yourself through the path structure until you found the file.Note: I haven't yet been able to confirm that this works, because I'd first need to wait for another Discord update. But hey, it's on the ArchWiki, so that's as good as it gets in terms of guarantees that something will work :)
1
Accedi per aggiungere un commento.
Commenti
12 commenti