Package Details: discord_arch_electron 0.0.78-1

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: 197
Popularity: 4.27
First Submitted: 2020-05-19 23:51 (UTC)
Last Updated: 2024-12-17 20:22 (UTC)

Dependencies (9)

Required by (25)

Sources (3)

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):
  • Switched back to the main electron package (electron22)
  • Watching cameras and streams is working again
Starting with 0.0.20-1 (2022-09-15):
  • Bumped electron16 to electron19 (I still have blocking issues with electron20)
  • Added support for $XDG_CONFIG_HOME/discord-flags.conf: this works like electron-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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 39 Next › Last »

Zoddo commented on 2024-05-05 20:19 (UTC)

@justbispo: Yeah, I haven't moved forward with including the patch following the SunRed's comment. I will get in touch with them.

justbispo commented on 2024-05-05 19:17 (UTC)

@Zoddo since the discord-electron was removed in favor of this one, I'll ask again, as it was asked before without an answer, if you could include Krisp support by including the patch support from either the still available discord-electron-openasar or the @SunRed's git repository.

Zoddo commented on 2024-04-16 17:52 (UTC)

Thanks for the report, I downgraded the package to electron29 until these segfaults can be investigated.

I got a stack trace for now, this seems to be an electron bug but nothing I can really report upstream without minimal reproduction steps.

#0  0x0000576d938ccb2d in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#1  0x0000576d938ccb1f in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#2  0x0000576d938ccb1f in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#3  0x0000576d938ccb1f in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#4  0x0000576d938ccb1f in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#5  0x0000576d938ccb1f in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#6  0x0000576d938ccb1f in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#7  0x0000576d938ccb1f in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#8  0x0000576d938ccb1f in views::View::UpdateChildLayerBounds(views::View::LayerOffsetData const&) ()
#9  0x0000576d938cba4e in views::View::SetBoundsRect(gfx::Rect const&) ()
#10 0x0000576d938ccdf4 in views::View::SetSize(gfx::Size const&) ()
#11 0x0000576d938ebce9 in views::Widget::OnNativeWidgetSizeChanged(gfx::Size const&) ()
#12 0x0000576d9391e688 in non-virtual thunk to views::DesktopNativeWidgetAura::OnHostResized(aura::WindowTreeHost*) ()
#13 0x0000576d9374aed2 in aura::WindowTreeHost::OnHostResizedInPixels(gfx::Size const&) ()
#14 0x0000576d9374cf58 in aura::WindowTreeHostPlatform::OnBoundsChanged(ui::PlatformWindowDelegate::BoundsChange const&) ()
#15 0x0000576d8e51aaef in electron::ElectronDesktopWindowTreeHostLinux::OnBoundsChanged(ui::PlatformWindowDelegate::BoundsChange const&) ()
#16 0x0000576d8eed4ad8 in ui::X11Window::DelayedResize(bool) ()
#17 0x0000576d8e724cb9 in void base::internal::CancelableCallbackImpl<base::OnceCallback<void ()> >::ForwardOnce<>() ()
#18 0x0000576d91ea7bfe in base::TaskAnnotator::RunTaskImpl(base::PendingTask&) ()
#19 0x0000576d91ec065c in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*) ()
#20 0x0000576d91ec0041 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() ()
#21 0x0000576d91ec0db5 in non-virtual thunk to base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() ()
#22 0x0000576d91f27eb2 in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) ()
#23 0x0000576d91ec1183 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) ()
#24 0x0000576d91e8d4fe in base::RunLoop::Run(base::Location const&) ()
#25 0x0000576d90cd728d in content::BrowserMainLoop::RunMainMessageLoop() ()
#26 0x0000576d90cd9113 in content::BrowserMainRunnerImpl::Run() ()
#27 0x0000576d90cd473c in content::BrowserMain(content::MainFunctionParams) ()
#28 0x0000576d8e6888c7 in content::RunBrowserProcessMain(content::MainFunctionParams, content::ContentMainDelegate*) ()
#29 0x0000576d8e68a2c2 in content::ContentMainRunnerImpl::RunBrowser(content::MainFunctionParams, bool) ()
#30 0x0000576d8e68a0b9 in content::ContentMainRunnerImpl::Run() ()
#31 0x0000576d8e6873d1 in content::RunContentProcess(content::ContentMainParams, content::ContentMainRunner*) ()
#32 0x0000576d8e6878ca in content::ContentMain(content::ContentMainParams) ()
#33 0x0000576d8e3320be in main ()

DodoGTA commented on 2024-04-16 14:26 (UTC)

@katt I recently updated to Electron 30 and Discord still works fine for me (so maybe this is some inconsistent behavior?)

katt commented on 2024-04-16 14:14 (UTC)

Not working with electron 30, just segfaults.

StarterX4 commented on 2024-04-11 19:43 (UTC)

Same for me, the log spam is massive

rkolbaskin commented on 2024-03-13 07:04 (UTC)

Is there any way to prevent it from log spamming "DiscordProcessObserver: Skipping '/usr/lib/electron29/electron'"?

Zoddo commented on 2024-03-11 19:44 (UTC)

For people having issues with wayland, I upgraded the package to use electron29 which includes a lot of fixes for wayland compared to electron26. Please tell me if you still experience crashes.

MagnificentSpam commented on 2024-03-09 12:09 (UTC)

I don't know what's happening, but one random data point: Discord would almost always fail to start with wayland until I removed "SKIP_HOST_UPDATE": true from the settings.json. With the updater it works for now, somehow.

DJXJD commented on 2024-03-07 23:17 (UTC) (edited on 2024-03-07 23:56 (UTC) by DJXJD)

As of the latest version, discord launches successfully very infrequently on wayland (outside of xwayland). Using the argument --no-sandbox makes the launch more likely to succeed.

More info: Before the update I was using vencord, and after the update vencord seemed to have been uninstalled. I tried repairing/installing/uninstalling vencord using the cli installer and thats when I started noticing problems. Downgrading to the previous version did not fix the problem. The first run after an upgrade or downgrade seems to always work.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 39 Next › Last »