Arch Linux User Repository

I'm not sure what's going on here. Anyone using the AUR is expected to know how makepkg works. Understanding what PGP keys are and what they mean to makepkg is part of this.

https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

That you guys apparently don't even realize what package you're building (going by all the libc++ comments posted here) is all the more surprising. Enable Brain 1.0, stop using AUR helpers and read the output on the damn console.

Any comments relating PGP keys, AUR helpers, or any topic which could be solved by reading the wiki will be deleted. Any upstream issues regarding Discord will similarly also be deleted. People who are stubborn about it will see their accounts suspended.

Please report issues with Discord itself to https://discord.gg/discord-testers or https://discord.gg/discord-linux.

Report any issues relating to the AUR package here.

buzo,

Anything is "possible", but moving a package to the official repos -- even when the license doesn't make that illegal -- is not and never has been about popularity.

It's about whether a Trusted User cares about the software enough to value personally investing in making it available. Not just about whether a Trusted User has been notified about ongoing abuse and stepped in to lay down the law...

As soon as you acquire Discord's permission to repackage and distribute Discord.

Alad, would it be possible to move such a popular package to the community repo then?

I'm not sure what's going on here. Anyone using the AUR is expected to know how makepkg works. Understanding what PGP keys are and what they mean to makepkg is part of this.

https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

That you guys apparently don't even realize what package you're building (going by all the libc++ comments posted here) is all the more surprising. Enable Brain 1.0, stop using AUR helpers and read the output on the damn console.

Any comments relating PGP keys, AUR helpers, or any topic which could be solved by reading the wiki will be deleted. Any upstream issues regarding Discord will similarly also be deleted. People who are stubborn about it will see their accounts suspended.

Is out of date

@test1265tester no it is not

Discord's emojis weren't rendering with the provided fonts. Replacing ttf-symbola with ttf-ancient-fonts did the trick.

I was having static/crackling whenever I joined voice chat until I came across this workaround: PULSE_LATENCY_MSEC=90 discord

Same error for me too! All 3 mic is dead

[000:000] [19727] (audio_send_stream.cc:519): Unable to create encoder for {name: opus, clockrate_hz: 48000, num_channels: 1, parameters: {stereo: 0, usedtx: 0, useinbandfec: 0}}

[000:000] [19727] (audio_send_stream.cc:261): Failed to set up send codec state. [012:529] [19727] (audio_send_stream.cc:519): Unable to create encoder for {name: opus, clockrate_hz: 48000, num_channels: 1, parameters: {stereo: 0, usedtx: 0, useinbandfec: 0}}

[012:529] [19727] (audio_send_stream.cc:261): Failed to set up send codec state. [012:534] [18531] (audio_coding_module.cc:1210): Add10MsData failed: No send codec is registered.

[012:534] [18531] (channel.cc:1323): ACM::Add10MsData() failed

The flatpak version works. Might be a packaging issue.

flower: I suggest that you ask upstream for support, since this does not look like a packaging issue to me.