Package Details: discord-electron-openasar 0.0.30+812-1

Git Clone URL: https://aur.archlinux.org/discord-electron-openasar.git (read-only, click to copy)
Package Base: discord-electron-openasar
Description: Discord packaged with OpenAsar using system provided electron (v24) for increased security and performance
Upstream URL: https://discord.com
Keywords: discord discord-stable discordapp electron openasar
Licenses: custom
Conflicts: discord
Provides: discord
Submitter: SunRed
Maintainer: SunRed
Last Packager: SunRed
Votes: 4
Popularity: 1.45
First Submitted: 2023-04-03 07:00 (UTC)
Last Updated: 2023-09-18 21:30 (UTC)

Required by (18)

Sources (3)

Pinned Comments

SunRed commented on 2023-04-19 19:58 (UTC)

If you run into problems (e.g. random segfaults) as I did when switching from the official client or the AUR versions using system Electron, make sure to remove all directories matching ~/.config/discord/*Cache and clean all Discord and Electron relevant directories in ~/.cache.

Latest Comments

SunRed commented on 2023-09-02 16:36 (UTC)

As I didn't announce it here when I updated the package: As of 0.0.29+812-2 Electron 24 is now used, segfaults due to arch repo's electron22 version shouldn't occur any longer. electron25 with this package resulted in unstable behavior again. As @Sukid mentions, in case of problems, try deleting ~/.config/discord first or at the very least ~/.config/discord/*Cache if you don't want to lose your session.

Sukid commented on 2023-09-01 21:32 (UTC)

@AsukaMinato If all else fails, delete the entire contents of the .config/discord directory. I haven't figured out which parts actually need deleting but just getting rid of everything with the word "cache" in it wasn't enough for me in particular.

(granted, I'm not using this package specifically -- I just put the download from the discord website in my .local/opt/ dir, replace the app.asar with openasar, and then have a launch script in .local/bin . Same idea overall just different method)

AsukaMinato commented on 2023-07-16 20:16 (UTC)

It keeps crashing.

✖  ELECTRON_ENABLE_LOGGING=1 discord
[OpenAsar > Init] OpenAsar nightly-cd44357
[OpenAsar > Settings] /home/w/.config/discord/settings.json {
  BACKGROUND_COLOR: '#202225',
  IS_MAXIMIZED: true,
  IS_MINIMIZED: false,
  WINDOW_BOUNDS: { x: 0, y: 71, width: 2048, height: 1081 },
  openasar: { setup: true, quickstart: true },
  trayBalloonShown: true
}
[OpenAsar > BuildInfo] { releaseChannel: 'stable', version: '0.0.27' }
[321086:0717/051323.229964:WARNING:wayland_object.cc(144)] Binding to wl_seat version 5 but version 8 is available.
[321086:0717/051323.230025:WARNING:wayland_object.cc(144)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available.
[321086:0717/051323.230080:WARNING:wayland_object.cc(144)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available.
[321086:0717/051323.348415:ERROR:browser_main_loop.cc(271)] Gdk: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
[OpenAsar > Modules] Checking
[321128:0717/051323.406972:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is egl, ANGLE is 
[321128:0717/051323.410577:WARNING:sandbox_linux.cc(380)] InitializeSandbox() called with multiple threads in process gpu-process.
[321086:0717/051323.424599:WARNING:wayland_surface.cc(149)] Server doesn't support zcr_alpha_compositing_v1.
[321086:0717/051323.424647:WARNING:wayland_surface.cc(164)] Server doesn't support overlay_prioritizer.
[321086:0717/051323.424651:WARNING:wayland_surface.cc(178)] Server doesn't support surface_augmenter.
[321086:0717/051323.424661:WARNING:wayland_surface.cc(212)] Server doesn't support zcr_color_management_surface.
[321086:0717/051323.425244:WARNING:cursor_loader.cc(133)] Failed to load a platform cursor of type kNull
[321086:0717/051323.430488:WARNING:xdg_activation.cc(86)] Cannot activate a window because no active windows found!
[321086:0717/051323.430550:WARNING:xdg_activation.cc(86)] Cannot activate a window because no active windows found!
[321086:0717/051323.438333:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[321086:0717/051323.809637:WARNING:electron_api_native_image.cc(175)] Failed to load image from path '/usr/lib/electron22/discord.png'
Optional module ./ElectronTestRpc was not included.
fish: Job 1, 'ELECTRON_ENABLE_LOGGING=1 disco…' terminated by signal SIGSEGV (Address boundary error)

SunRed commented on 2023-06-02 20:00 (UTC)

The launch script now includes a rudimentary patch that allows for Krisp noise suppression support.

SunRed commented on 2023-05-27 19:01 (UTC)

I updated this package with a new launch script (Thanks to Zoddo / discord_arch_electron) that loads a config file for custom Electron flags and fixed a few other minor issues. With the latest Electron 22 release 22.3.11 (that still has to be updated on the Arch repos) the strange bug that leads to a segfault/crash on maximising the window on Wayland is fixed.

Cheers.

SunRed commented on 2023-04-19 19:58 (UTC)

If you run into problems (e.g. random segfaults) as I did when switching from the official client or the AUR versions using system Electron, make sure to remove all directories matching ~/.config/discord/*Cache and clean all Discord and Electron relevant directories in ~/.cache.

SunRed commented on 2023-04-03 13:54 (UTC)

@KokaKiwi yes, but weirdly enough the application segfaults in my case with electron 22 that I have not yet run through a debugger. It doesn't seem to happen with the normal discord(-electron) package. Using the additional chromium flags doesn't seem to make a difference so I let them be though ideally I would want to replace this hard configuration of flags with a config file, unrelated to the problem.

KokaKiwi commented on 2023-04-03 09:01 (UTC)

Shouldn't the package depends on electron22, as the electron version used by the upstream Discord package?