What is the best way to install Discord, that keeps it updated automatically? Or Vesktop?

I have taken a look through the forum, and I can see various people installing Discord/Vesktop in either Fedora or Debian templates, but im unsure what to do. I can see some people recommend snap but I don’t really want to use canonicals snap, and if I install a .deb file for Discord, will it auto update? If not, what are my other choices?

I also tried installing it via the rpmfusion repos in a clone of the default fedora-44-xfce template, but I couldn’t find the package with dnf search so I just deleted it for now.

What is the best way to go about this?

I also plan on following the Gaming HVM guide to setup passthrough for my NVIDIA card and use the intel iGPU on the CPU for dom0, what is the best way to install steam for this as well?

Welcome to forum

I have installed it before, and it is updatable.

I don’t recall which version it was, but updates came directly through the application itself—not via Snap or any other OS-level package management systems.

Have you tried downloading from the official Discord website?

It might be better to post your issue within the guide’s discussion threads—that way, it can help both you and others who have the same question.

Thanks for your reply.

I have not tried the builds on the discord.com website, however I do see they have .rpm and .deb builds. Would you recommend just using these? Or would it be better to go ahead and configure flatpak and install that way instead?

I would install Discord on flatpak using --user flag in AppVM.

For discord, i create a standalone base from debian template and install it with .deb (as i remember).
The update is ok…

I am trying to wget the .deb file provided by Discord however the URL provided by discord.com, I can’t wget the .deb file directly from my terminal via the debian template I have cloned/am using. Is there an additional step to this that I am missing?

Discord updates itself on every run, so you can install it in a template if you don’t mind facing an update every time you launch it. Reinstall when the update process starts taking too long.

Thank you for your help everyone. I just downloaded the .deb for Discord in a disposable VM and copied it to my untrusted AppVM template and installed it. (Which is just a clone of debian-13-xfce). Then booted up untrusted, refresh applications, then add Discord to it’s app menu/list. Seems to be working fine.

Hi. I’m an avid user of both Qubes and Discord, and I’m happy to share that I’ve long since figured this one out.

Create a standalone qube based on the Debian template. Then install flatpak:

sudo apt install flatpak

Then, download the Discord .flatpakref repository from Flathub:

Then, install downloaded .flatpakref package on your system:

flatpak install com.discordapp.Discord.flatpakref

Then you should be good to go.

Wouldn’t this install Discord system/vm wide instead of just for the user? And I don’t believe this updates automatically, you would need to run flatpak update

You don’t need to run flatpak update. Discord automatically updates every time it opens. And yes, my solution is for running in a standalone VM that’s used for Discord only. That’s the purpose of Qubes, isn’t it?

Thank you, I would prefer to use flatpaks/flatseal for the additional sandboxing as well anyways so I might change my setup in the future. But for now, the .deb in it’s own template works fine.

The reason I went with the standalone VM instead of the template is because Discord can update itself at launch when it’s running in a standalone VM, but updating a template-based Discord requires booting and running updates in the separate template VM.

@qubesuser123456

I think you may be misinterpreting how this setting works.

No, I’m not misinterpreting. If you install Discord in a template, then you will have to update every time you launch your appVM, unless you separately update your template. If you create a standalone VM just for Discord, locally applied updates will be saved persistently in your standaloneVM, and you won’t have to re-apply the updates every time you launch Discord, nor will you have to manage Discord updates in your template.

Flatpak’s good. You can also use Discord in the browser, that has served me well. I have a .desktop file for running it in Kiosk mode, which makes it almost seamless.

[Desktop Entry]
Version=1.0
Type=Application
Name=Discord-Kiosk
GenericName=Discord (Kiosk)
Comment=Open Discord in Firefox kiosk mode (no browser chrome)
Exec=firefox -kiosk "https://discord.com/channels/@me"
TryExec=firefox
Terminal=false
StartupNotify=true
Icon=discord
Categories=Network;InstantMessaging;WebBrowser;
Keywords=discord;chat;voice;video;gaming;messages;
StartupWMClass=firefox