@Thaodan: The resource folder was asked by irisnk in this comment.
That sounds like a hack. If one wants openasar they should install discord patched with openasar... But not my call what he wants to do.
Git Clone URL: | https://aur.archlinux.org/discord_arch_electron.git (read-only, click to copy) |
---|---|
Package Base: | discord_arch_electron |
Description: | Discord (popular voice + video app) using the system provided electron for increased security and performance |
Upstream URL: | https://discord.com |
Keywords: | chat discord discord-stable discordapp electron video voice |
Licenses: | custom |
Conflicts: | discord |
Provides: | discord |
Submitter: | johnnyapol |
Maintainer: | Zoddo (Thaodan, SunRed) |
Last Packager: | Zoddo |
Votes: | 189 |
Popularity: | 4.99 |
First Submitted: | 2020-05-19 23:51 (UTC) |
Last Updated: | 2024-05-06 19:01 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 35 Next › Last »
@Thaodan: The resource folder was asked by irisnk in this comment.
That sounds like a hack. If one wants openasar they should install discord patched with openasar... But not my call what he wants to do.
@Thaodan: The resource folder was asked by irisnk in this comment.
Why keep the resources folder? Electron doesn't care for the folder name, /usr/share/discord is enough.
Discord is architecture-dependent (it dynamically downloads native modules compiled for x86_64 on the first run). The asar archive doesn't contain anything architecture-dependent by itself, so I will move it to /usr/share/discord/resources/ on the next package update,
The discord package e.g. the host part of the package is not architecture dependent. Without the precompiled Electron it still runs on architectures (minus the features that require native node modules).
@zoddo No problem! I figured I would report on it since the last report was some time ago.
Discord is architecture-dependent (it dynamically downloads native modules compiled for x86_64 on the first run).
The asar archive doesn't contain anything architecture-dependent by itself, so I will move it to /usr/share/discord/resources/
on the next package update, but I believe the PKGBUILD should continue to use arch=('x86_64')
since the package will not run on other architectures.
@Mewio: Thanks for the report, I'll take a look at the pop-out issue.
Since the asar isn't architecture dependent shouldn't it be installed to /usr/share instead of /usr/lib?
For the past two years, I have been unable to use this package simply because popping out streams does not work. I need that for work and obviously with friends. This has always happened on any fresh (or not fresh) install of Arch on multiple machines and devices. It has also been reported previously by other users. I simply created an account here to remind about it. When you pop out a stream, the audio will continue to play but the stream it self will only show that it is buffering. Streams work fine when not popped out but unfortunately then the streams are too small do to parts of discord not being collapsable. I can work around this by abusing KDE's fullscreen shortcut (if you use chromium/electron's built in fullscreen then use KDE's shortcut to fullscreen, it will run the fullscreened chromium in a window.)
I can think that extracting the asar could remove some duplicates when fdupes is used and allow deduplication to work better.
Why do you install discord to /usr/lib? It doesn't contain any architecture specific files.
@irisnk: Thanks for the report. I did better and moved these resource files to the resources
subdirectory.
On an unrelated note, I've also removed the --unpack-dir '**'
option to the asar pack
invocation to allow files to be packed in the archive. I'm not sure why this option was present (it was added in the first version that extracted the asar archive), but it's not required and prevents files from being compressed on disk.
Could you please sudo ln -s /usr/lib/discord /usr/lib/discord/resources to make automated openasar installers (like openasar-bin and the vencord installer script) work again? Thanks in advance!
Pinned Comments
Zoddo commented on 2022-09-15 17:54 (UTC) (edited on 2023-03-31 17:24 (UTC) by Zoddo)
Starting with 0.0.26-1 (2023-03-31):
Starting with 0.0.20-1 (2022-09-15):
$XDG_CONFIG_HOME/discord-flags.conf
: this works likeelectron-flags.conf
, you can set in this file the command line flags you want to pass to electron when running Discord (there are some useful flags in the wiki, especially if you are experiencing lag in the Discord UI).FAQ
Discord requires an update, but this package isn't yet updated
Check the wiki.
The Discord UI is lagging
Try to add the flags recommended in the wiki in
$XDG_CONFIG_HOME/discord-flags.conf
.Krisp not working
This is an issue that will likely never be fixed for this package. The Krisp module checks if Discord binaries are signed by Discord, which is not the case with this package.
See this comment and this GitHub issue for more details and possibles workarounds.