Is it possible to get notifications to appear as "Discord", not Electron?
https://i.imgur.com/vFaVADj.png is how the notifications appear under KDE.
Git Clone URL: | https://aur.archlinux.org/discord_arch_electron.git (read-only, click to copy) |
---|---|
Package Base: | discord_arch_electron |
Description: | Discord using 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: | 195 |
Popularity: | 5.09 |
First Submitted: | 2020-05-19 23:51 (UTC) |
Last Updated: | 2024-11-19 19:20 (UTC) |
« First ‹ Previous 1 .. 30 31 32 33 34 35 36 37 38 Next › Last »
Is it possible to get notifications to appear as "Discord", not Electron?
https://i.imgur.com/vFaVADj.png is how the notifications appear under KDE.
EDIT: it was caused by firejail. My config was to start every program by firejail with onetime setup #firecfg. After cleaning the entries with firecfg --clean discord started without any problem. Although one or two months ago, I was able to start discord with firejail enabled.
My discord will not start. When I use the .desktop file, nothing happens.
Typing discord in terminal and I will get this:
Reading profile /etc/firejail/discord.profile
Reading profile /etc/firejail/discord-common.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-exec.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-common.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Seccomp list in: !chroot, check list: @default-keep, prelist: unknown,
Parent pid 8486, child pid 8487
Warning: skipping discord for private /opt
Private /opt installed in 0.17 ms
14 programs installed in 26.69 ms
Warning: skipping alternatives for private /etc
Warning: skipping crypto-policies for private /etc
Warning: skipping password for private /etc
Warning: skipping pki for private /etc
Private /etc installed in 46.94 ms
Warning: skipping alternatives for private /usr/etc
Warning: skipping ca-certificates for private /usr/etc
Warning: skipping crypto-policies for private /usr/etc
Warning: skipping fonts for private /usr/etc
Warning: skipping group for private /usr/etc
Warning: skipping ld.so.cache for private /usr/etc
Warning: skipping localtime for private /usr/etc
Warning: skipping login.defs for private /usr/etc
Warning: skipping machine-id for private /usr/etc
Warning: skipping password for private /usr/etc
Warning: skipping pki for private /usr/etc
Warning: skipping resolv.conf for private /usr/etc
Warning: skipping ssl for private /usr/etc
Private /usr/etc installed in 0.20 ms
Warning: cleaning all supplementary groups
Warning: cleaning all supplementary groups
Warning: cleaning all supplementary groups
Warning: /sbin directory link was not blacklisted
Warning: /usr/sbin directory link was not blacklisted
Seccomp list in: !chroot, check list: @default-keep, prelist: unknown,
Child process initialized in 151.11 ms
/usr/bin/discord: line 2: exec: electron: not found
Parent is shutting down, bye...
Would it be possible to fix the naming convention of the running progress, in order to better support Beautifuldiscord?
It looks for the running executable, normally named 'discord', but this package makes it run under electron.
The tag under ps -eo comm=,
is what I believe to be the trigger.
@Kyuunex there is a temporary solution. If you highlight the entire word before you right click on it, the spellchecker will show suggestions.
spellcheck on this seems to be partially broken compared to the official, untouched discord. it does show the red underlines but it does not show suggestions
Nevermind, since I'm using the electron-ozone
package, I think I just need to compile the latest version with the icu68 patch and it will use icu
68 from core.
I had the same issue as @solace but discord was looking for version 67 of the lib. Since there's no icu67 package, I've created one, installed it and now discord runs.
My error was
electron: error while loading shared libraries: libicui18n.so.67: cannot open shared object file: No such file or directory
So if you're having the same problem as me, you can add icu67
to your dependencies.
Newest electron update (electron6-6.1.12-3) breaks discord electron. Discord fails to open. This is the output I get when I try to run it: electron: error while loading shared libraries: libicui18n.so.68: cannot open shared object file: No such file or directory
@fadedave Facing a simillar issue, seems to be releated to arch's electron update and betterdiscord. Looking through the electron dev console there is always an error saying:
Unable to load preload script: /home/$USER/.config/discord/0.0.13/modules/discord_desktop_core/injector/betterdiscord/preload.js
Removing betterdiscord fixes the issue.
Unfortunately Im not proficient enough in js to figure it out from there. Anyone have ideas?
Launching discord_arch_electron, I get the error message "Your installation is very out of date", and it doesn't let me use discord. The same version of the official app works fine.
Pinned Comments
SunRed commented on 2024-06-09 20:34 (UTC)
After a chat with @Zoddo and me just taking too long to come back to this, there should everything now be included that was in my old
discord-electron
package some migrated from (Krisp patcher, Wayland, autostart fix). Additionally I replaced the scrappy rizin patcher with a Python script someone from the nix community kindly made available.Instead of checking against a checksum to know whether the Krisp binary was patched the script is run on every start of the client that results in slightly longer start times but has the advantage that we don't have to update the package if Discord ever silently updates the binary between client updates over their modules api.
Cheers
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.