Arch Linux User Repository

I actually remember seeing that messages before. But I don't see them with current electron24-bin verison (24.0.0.beta.3-2).

Btw you can also test webcord-bin.

Thanks for the PKGBUILD tip, that's going to be very helpful!

I don't know if it's a issue with webcord itself still, I've just tried checking chrome://gpu on electron24 and the issue still seems to persist, even if I force hardware acceleration on via command line arguments/flags. I understand the switch here was done because webcord's latest official release officially made the jump to electron 24 and there seems to be no other package providing it either on the official repos or AUR, but maybe the electron24-bin AUR package listed as a dependency is broken?

Does anyone else have this issue? If it's not just me, I'll report this on electron24-bin's AUR page!

The switch to Electron 24 seems to have broken hardware acceleration for me

I think it is better to be reported upstream.

Forcing webcord to run using Electron 22 by editing /usr/bin/webcord fixes the issue

You can switch version in PKGBUILD, edit this line:

_electron='electron24'

The switch to Electron 24 seems to have broken hardware acceleration for me, resulting in very bad performance during screensharing/video calls. The page chrome://gpu reports all kind of hardware acceleration to be off and webcord reports this error in the terminal:

[62561:0413/202010.997321:ERROR:gl_factory.cc(128)] Requested GL implementation (gl=desktop-gl,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].

[62561:0413/202010.998776:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization

Forcing webcord to run using Electron 22 by editing /usr/bin/webcord fixes the issue

Probably goes without saying, but deleting config.json will delete webcord's settings, so if you've enabled/disabled certain permissions you'll have to redo those.

Edit: also FWIW I didn't have to delete this file, YMMV

Update 4.2.0 wants to use Electron 24 only, so deps are changed accordingly.

Also for me deleting old config.json was required to run the app.

@kronikpillow, this is developer's statement, not mine.
Official builds are made with Electron 22. You can try the official build via webcord-bin to test does it work better for you.

@kronikpillow This isn't just a random comment Hanabishi decided on, if you check upstream this how they specify the compatibility (they allow anywhere from electron 18 to 22).

So if you're having issues with a specific version I would talk with upstream especially for the newer electron versions.

I disagree with @Hanabishi's comment that it's compatible with a wide range of electron versions, on v22 webcord crashes as soon as you open the settings page of webcord ... on v21 it just randomly crashes on it's own, now I'm testing with v20 ... wish there was a note on which version is actually supported so that we would actually use a working version

This isn't the right way to handle this, it's a required dependency so it should be specified using version ranges: depends=('electron>=17' 'electron<23')

I agree, if it would have worked.

Edit: nevermind, looks like the electron packages are structured weirdly and don't provide electron so this has to be the way.

Exactly. If someone has better idea, you are welcome.