I can’t be the only one with this problem, but I didn’t see any threads on this topic. What is the normal way to install Discord on Fedora (39 in my case)? The rpm and flatpak versions of Discord seem to be unusable, since reasonably often Discord won’t start because there is an update that hasn’t yet made it into the repo. It looks to me like the only feasible way to install Discord is from the official tarball (or the .deb, but I fear that might be more problematic), so that when there is an update I at least can do the update manually. Is that how everyone is doing it and I just didn’t get the memo?
I’m not a Discord user but I’m looking at the Flathub page and it is packaged by the Discord team. If that isn’t working it seems like you could get support directly from them. Otherwise perhaps try installing the deb in Distrobox, I’d be interested if that worked.
1 Like
No problem with discord from flathub, other than discord bombarding me with all kinds of offers and news at every start …
I have installed discord as `–user’, and yes, discord applies some updates on start somewhere. Do you use a system install, and does that prevent discord’s own update thingy by any chance?
Do you use a system install, and does that prevent discord’s own update thingy by any chance?
While Discord does do its own updates at start up, every now and then it insists on a larger update being downloaded separately.
It looks to me like the only feasible way to install Discord is from the official tarball
That’s the route I went down. It expects to be unpacked in /usr/share/discord/, or you can pick a more convenient folder for yourself and edit the launcher to match.
If Discord have a flatpak that they’re managing, that’s probably the easiest route though.
May not be the easiest method and surely won’t even be recommended (since you may need to manually install the necessary dependencies), but for my part I prefer to use the tar.gz archive provided on their website.
Once I download the archive I copy it to the /opt path and extract it, then simply run it via terminal or create a custom desktop entry and start it normally clicking the icon on the menu.
I use the Discord flatpak from Flathub and I don’t recognize the issue you’re having in my instance. Could you have two separate instances of Discord installed, one from the flatpak and another from somewhere else, which could cause you to get mixed up as to which one you’re running?
I don’t think so. I tried the rpm discord and had this problem, then the flatpak one. Both were supposed to be uninstalled, as I was just using the web version. That said, something funny is going on, as when I searched for the flatpak one to see where it came from (flathub, as it turns out) it said it was not installed but had files left laying around. That’s odd, so maybe I screwed up my testing and caused my own problems. I’ll reinstall and see what happens. Or that’s what happens when it tries to upgrade without being able to do it, I dunno. Will find out.
OK, so this is odd. I made sure everything was uninstalled, then installed Discord from flathub. When I run it from the start menu, it begins downloading updates, but eventually just terminates. Same if I do it via ‘flatpak run’. I hoped the latter would give me a useful error message, but it does not. That’s weird, but it gets weirder: I installed Vesktop on a whim, since it has five stars and the official client only has four, and that seems to run fine. ???
The reason I prefer to use tarball is because I have experienced the same problem myself.
Discord requires to be updated by forcing the download of tarball from their website which however doesn’t go to update the flatpak or rpm version released via rpmfusion, but being obviously unofficial releases it’s also understandable that new updates are not guaranteed to be released in real time.
The solution could be the one suggested on this forum:
Disabling Discord update check/forced updates on Linux
that is to disable the checks for the presence of new versions and wait for updates released by flatpak or rpmfusion, although flatpak should already use this workaround for its version
I got the same issue resolved by installing the Nvidia driver. The easiest way to install the NVIDIA driver on Fedora is through the RPM Fusion repositories, which provide the latest proprietary drivers.
sudo dnf install https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf install https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
Then install the driver,
sudo dnf install akmod-nvidia
And reboot the system,
sudo reboot
Verify your installation with,
nvidia-smi
You might need to disable the secure boot and reboot the system if nvidia-smi failed. After all, then try installing Discord using flatpak.
Just in case some of you don’t know, Discord is actually just a website, so what the packaged versions generally do is ship a complete copy of a webbrowser like Chrome or Firefox with the Discord site preloaded.
As an alternative you can simply go to discord.com/app in a regular browser and you will have the full Discord experience.
Some browsers will also let you pin URLs as a standalone ‘web app’ if you prefer that. You can however also use it in a normal tab or window.