Skip to content

discord: fix to find updater_bootstrap#60631

Open
Techno263 wants to merge 1 commit into
void-linux:masterfrom
Techno263:discord-1.0.138_2
Open

discord: fix to find updater_bootstrap#60631
Techno263 wants to merge 1 commit into
void-linux:masterfrom
Techno263:discord-1.0.138_2

Conversation

@Techno263
Copy link
Copy Markdown

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, x86_64-glibc

@Duncaen
Copy link
Copy Markdown
Member

Duncaen commented May 19, 2026

Can you explain why each change is needed?

@Techno263
Copy link
Copy Markdown
Author

Techno263 commented May 19, 2026

I'm not sure how this is working for others, but when I launch discord through the /usr/bin/discord symlink the executed script fails because it cant find updater_bootstrap.

When trying to find updater_bootstrap it checks three places: /usr/share/discord/updater_bootstrap, /opt/discord/updater_bootstrap, and $(dirname -- "$0")/updater_bootstrap. When launching through the symlink the last path resolves to /usr/bin/updater_bootstrap and fails. If the symlinks real path is gotten before calling dirname the final path will be /usr/lib/discord/updater_bootstrap. Which finds updater_bootstrap and executes successfully.

@Techno263
Copy link
Copy Markdown
Author

The symlink change in the template is because the discord application filename capitalization changed in the 1.0 release; from Discord to discord. On my system the symlink with a capital D is broken because of that.

@Techno263
Copy link
Copy Markdown
Author

Techno263 commented May 19, 2026

I'm guessing others maybe using the desktop entry to launch discord, but I am puzzled how the Exec=/usr/bin/discord part of it runs successfully.

Edit: nevermind, I was looking at the desktop entry discord releases. I forgot the Exec entry gets patched when packaging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants