Arch Linux

kholo

Member

Registered: 2011-05-16

Posts: 5

Discord autostart with a wrong path after each update

Hello,

I encounter the same issue for a while now, after every package update, using the regular discord package from the extra repository.
I'm using KDE, and the application has autostart enabled, creating an entry in the Autostart section from the System Settings, but I don't think this is related to KDE as it's a .desktop file created in the $HOME/.config/autostart directory.
After each update, the Exec path is set to something like $HOME/.config/discord/app-X.X.XXX/Discord, X.XX.XXX being the previous version, not the newly installed, making Discord not to run at session start.
I always set it back to /usr/bin/discord but I don't understand this behavior.

Does anyone run into the same issue?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,841

Re: Discord autostart with a wrong path after each update

but I don't think this is related to KDE as

… session re/storage is disabled?
Does this happen if you explicitly close discord before logging out / shutting down?

Why is the executable stored in ~/.config/discord/app*/Discord at all?
https://archlinux.org/packages/extra/x86_64/discord/ ships usr/bin/discord and usr/share/applications/discord.desktop - symlinking the latter into https://wiki.archlinux.org/title/XDG_Autostart should™ autostart discord and if discord has some internal option to fudge autostarting, just disable that.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

kholo

Member

Registered: 2011-05-16

Posts: 5

Re: Discord autostart with a wrong path after each update

Why is the executable stored in ~/.config/discord/app*/Discord at all?

This I don't understand. I only installed the discord from Archlinux repository. Could it be an in-app update that would have fired and set itself as the new default Discord?

if discord has some internal option to fudge autostarting, just disable that

Indeed when I toggle the autostart option from within Discord (being run from /usr/bin), it creates a desktop entry in the .config/autostart, where the ExecBin targets the .config/discord/app-X.XX.XXX/Discord file.
I untoggled the option and created manually the symlink to the package desktop entry, then when restarting Discord, it considers the option being toggled on again. Won't it overwrite the autostart entry during next update (using pacman/wrapper)? I'll wait and see.

If it does, I'll remove the package and the whole .config/discord directory, I'll reinstall it and see if the behavior differs.

I was just wondering if anyone encountered the same behavior, and if anyone did, if they know what fires it.