Discord
Discord is a proprietary, cross-platform, all-in-one voice and text chat application. Many open-source communities have official Discord servers as well. Discord can be used through a web browser or through the desktop application, which is made with Electron.
Installation
You can use one of the following packages to install the desktop application for Discord:
Warning: The usage of third-party clients, or any unofficial package or application that modifies the Discord client, is against Discord’s Terms of Service and may get your account banned [1]. You take all responsibility when using such packages. Avoid using outdated or abandoned clients, as they are more likely to trigger Discord’s anti-spam system in their API and thus get your account banned.
Graphical clients
Official applications
Alternatively, Discord is available as a Flatpak. This may fix some issues related to system libraries and improve performance in some cases, but needs some extra work to enable Rich Presence. See #Enabling rich presence on Flatpak.
$ flatpak install discord
Official clients using system electron
Official clients, using the system provided electron for increased security and potentially better performance:
- Stable: discord_arch_electronAUR
- Nightly: discord-canary-electron-binAUR
Third-party clients
- Abaddon — An alternative Discord client made with C++/gtkmm with voice support.
- discord-screenaudio — A custom discord client that supports streaming with audio on Linux.
- Fast-Discord — A new Discord client made in C++ and Qt. Discontinued on Feb 26, 2023.
- gtkcord4 — GTK4 Discord client in Go.
- Ripcord — A lightweight, proprietary desktop chat client for group-centric services like Slack and Discord built upon the Qt toolkit.
- WebCord — Wrapper for the web client that improves privacy and allows for screensharing on Wayland.
- ArmCord — A custom client designed to enhance your Discord experience while keeping everything lightweight.
Command-line clients
There are numerous CLI-based third party clients on the AUR (and non-packaged ones on Github), although most are deprecated or broken. discordo is maintained and packaged on the AUR as discordo-git AUR .
Chat client plugins
- purple-discord — Discord plugin for libpurple based messengers such as Pidgin
- bitlbee-discord — Discord plugin for Bitlbee
- weechat-discord — Discord plugin for WeeChat
Custom CSS & plugins
- BetterDiscord — A project which allows Discord to be modified to use custom CSS and plugins.
- Discocss — A simple script that can inject custom CSS into Discord clients. To inject CSS into the discord-ptbAUR and discord-canaryAUR versions, replace any mentions of the discord folder with the version in use.
- Replugged — A fork of Powercord, the lightweight discord client mod focused on simplicity and performance.
- VenCord — A Discord client mod that loads entirely before Discord’s boot—aiming to make it faster and more stable.
Overlay
For Linux clients, Discord does not support in-game overlay. discover-overlay AUR is an open-source GTK application that provides these functions. Discover works on X11 or wlroots environments.
Utilities
- Chuncord — A command line tool to upload files to the Discord CDN in parts using webhooks
Tips and tricks
GNOME top bar icon
If you would like to have the icon on the top bar of GNOME, install the AppIndicator and KStatusNotifierItem Support extension and libappindicator-gtk3 .
Discord asks for an update not yet available in the repository
Discord will refuse to launch if there is an update available, and the following message will be shown «Must be your lucky day, there’s a new update!». If the updated version is not yet available in the official repos, you can build and install the updated package using the Arch build system.
To disable the update check, add the following to ~/.config/discord/settings.json :
~/.config/discord/settings.json
"SKIP_HOST_UPDATE": true
Note that you will need to add an extra comma after the «WINDOW_BOUND» array due to JSON requirements, i.e.:
< "IS_MAXIMIZED": true, "IS_MINIMIZED": false, "WINDOW_BOUNDS": < "x": 2240, "y": 219, "width": 1280, "height": 720 >, "SKIP_HOST_UPDATE": true >
Start Discord minimized
Discord can be started minimized through the —start-minimized argument.
Microphone noise suppression
Discord now has noise suppression built in, with both a standard option and an AI-powered option provided by Krisp. You can also provide your own noise suppression on PipeWire by following PipeWire#Noise suppression for voice.
Screen sharing with audio
This article or section is out of date.
Reason: Discord’s intent is to eventually provide native audio sharing via PipeWire. [2] (Discuss in Talk:Discord)
This article or section needs expansion.
Reason: This looks like a good starting point for setting up PipeWire audio routing: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Virtual-Devices#create-a-sink (Discuss in Talk:Discord)
Screen sharing with audio is not officially supported on Linux. One alternative to this is to route the application audio through your microphone:
- For PulseAudio, following PulseAudio/Examples#Remapping select audio sources to obtain a Monitor of source for the program to share, which can be used as input for another instance of Discord running in a browser.
Another approach is to use a modded client that will feed the audio into the Discord stream rather than mixing it in with the microphone:
- For PipeWire, a current workaround, and most likely the easiest way to use audio screen sharing, is to use discord-screenaudioAUR .
Warning: Modded clients are against the Discord Terms of Service; see #Installation for more details.
Enabling Developer Tools
Warning: Code that is pasted into the Console of the developer tools has the ability to steal your credentials and compromise your Discord account. Do not enable this unless you know what you are doing.
After a recent update, devtools were disabled by default on Discord for safety reasons. To re-enable them, add this to ~/.config/discord/settings.json :
"DANGEROUS_ENABLE_DEVTOOLS_ONLY_ENABLE_IF_YOU_KNOW_WHAT_YOURE_DOING": true
Enabling Text-to-Speech
By default, Text-to-Speech is disabled in the Discord client. However, it can be enabled using the —enable-speech-dispatcher flag. This utilizes the speech-dispatcher daemon to output the speech.
Troubleshooting
Lagging when scrolling through your guilds
If you experience lags and stutters while scrolling through your guilds please ensure that your hardware acceleration is working correctly. You can do this by opening chrome://gpu in a Chromium based browser. If it is not working please check the chapter on Hardware video acceleration and try running Discord with some additional options:
$ discord --ignore-gpu-blocklist --disable-features=UseOzonePlatform --enable-features=VaapiVideoDecoder --use-gl=desktop --enable-gpu-rasterization --enable-zero-copy
Crackling during voice calls
If you experience crackling sounds when in voice chat, try the steps outlined in PulseAudio/Troubleshooting#Troubleshooting buffer underruns (glitches, skips, crackling).
Screen sharing on Wayland
As of version 0.0.17, the Screen Share feature does not work on Wayland, even when enabling Ozone for Wayland using /usr/bin/discord —enable-features=UseOzonePlatform —ozone-platform=wayland . See this Reddit post and the Discord bug report.
As a work around webcord AUR can be used which fully supports screensharing on Wayland, however lacks features like rich presence as it bundles the web version of Discord. The web version itself may also be used.
Another alternative is Vesktop, available at vencord-desktop-bin AUR . (Warning: Vesktop comes with Vencord preinstalled, a client mod, which is against the TOS and might get your account terminated. Use at your own risk)
Enabling rich presence on Flatpak
When using the Flatpak version of Discord, Rich Presence will not work out of the box. To make it work, it is necessary to create a symlink from $XDG_RUNTIME_DIR/discord-ipc-0 to $XDG_RUNTIME_DIR/app/com.discordapp.Discord/discord-ipc-0 . To create the symlink for the current user session, run:
$ ln -sf /discord-ipc-0
To automatically create the symlink, systemd-tmpfiles can be used by adding the following line to a file with the .conf extension in ~/.config/user-tmpfiles.d/ :
L %t/discord-ipc-0 - - - - app/com.discordapp.Discord/discord-ipc-0
Discord becomes unresponsive during long calls
If Discord becomes unresponsive during long calls, try the —no-sandbox argument. You can also add the following to your .bashrc, or alias file for your shell:
alias discord='discord --no-sandbox'
Discord freezes after getting pinged or messaged
If a message that would trigger a notification (pings, DMs, servers with notifications on, etc) causes the client to freeze, the client is failing to find a notification server. To fix it without installing a notifications server, disable Enable Desktop Notifications in the Notifications options.
Notification sounds do not work with PipeWire
Emojis are not rendered correctly
If you encounter rendering issues regarding emojis (rendering as rectangles for example), discord-canary-electron-bin AUR has the appropriate fonts as optional dependencies. You should install ttf-symbola AUR , noto-fonts-cjk , and noto-fonts-emoji .
ttf-twemoji AUR is required for emoji to appear in channel names. Be sure to install 75-twemoji.conf to /etc/fonts/conf.d/ , which doesn’t happen by default.
Clicking link does not open the web browser
If clicking a link does not open a tab in your default web browser, you should install the xdg-utils optional dependency.
Sync with computer feature not working
Discord is parsing the following file to find which theme to apply:
$HOME/.config/gtk-3.0/settings.ini
and it is looking for these specific lines:
[Settings] gtk-theme-name=Adwaita-dark
If you change the theme from Adwaita-dark to Adwaita, then Discord will automatically change to light version and vice-versa.
Note that Discord only supports a few popular themes, so if it does not work for your particular theme (in this example with Materia theme), a «dirty» fix would be to put the following in your settings.ini file:
[Settings] gtk-theme-name=Adwaita-dark gtk-theme-name=Materia-dark
The definition order is important because GTK will use the second variable definition so in this case Materia-dark but Discord will still successfully detect that you are using a dark theme by providing Adwaita-dark in the first variable definition of the GTK theme.
Blurry Discord icon in KDE Plasma system tray
You can attempt to fix this issue by installing libappindicator-gtk3 to replace libappindicator-gtk2 , which is known to cause this issue.
Discord spams systemd journal
You may find that Discord creates a lot of messages in your journal in a format like:
(device_info_linux.cc:45): NumberOfDevices
To disable the logging that causes this pollution: go to User Settings, select «Voice & Video», scroll to bottom of the screen and disable «Debug Logging».
No voice chat in a pure-ALSA environment
Discord’s desktop application relies on PulseAudio for voice chat and does not run on ALSA directly. Using apulse as a workaround is, in this case, deprecated. If you want to use Discord’s voice chat without PulseAudio or Pipewire, access Discord’s web client through a Chromium-based web browser. Alternatively, as a Chromium-based wrapper, Webcord works in pure-ALSA environments.
If you choose this route and are unable to unmute, i.e., to get permission to access your microphone, set it as default capture device in ~/.asoundrc . Also, in Discord, go to User Settings > Voice & Video > Input Device, and make sure Default is selected.
Notification badge is missing
Discord can display a badge showing the number of unread mentions on the taskbar icon. If the badge is not displayed, verify that the libunity AUR package is installed, as it is required for this feature to work.
Black screen on Wayland on NVIDIA proprietary driver
Discord on Wayland requires VA-API support, which the NVIDIA proprietary driver does not have. A translation layer such as libva-nvidia-driver can be used to get VA-API support.
Note: libva-vdpau-driver may not work due to a regression introduced on NVIDIA driver series 530.
Retrieved from «https://wiki.archlinux.org/index.php?title=Discord&oldid=792214»
Introduction #
Poetry is a tool for dependency management and packaging in Python. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you. Poetry offers a lockfile to ensure repeatable installs, and can build your project for distribution.
System requirements #
Poetry requires Python 3.8+. It is multi-platform and the goal is to make it work equally well on Linux, macOS and Windows.
Installation #
Poetry should always be installed in a dedicated virtual environment to isolate it from the rest of your system. In no case, it should be installed in the environment of the project that is to be managed by Poetry. This ensures that Poetry’s own dependencies will not be accidentally upgraded or uninstalled. (Each of the following installation methods ensures that Poetry is installed into an isolated environment.)
If you are viewing documentation for the development branch, you may wish to install a preview or development version of Poetry. See the advanced installation instructions to use a preview or alternate version of Poetry.
- With pipx
- With the official installer
- Manually (advanced)
- CI recommendations
pipx is used to install Python CLI applications globally while still isolating them in virtual environments. pipx will manage upgrades and uninstalls when used to install Poetry.
pipx install poetry pipx install pipx can also install versions of Poetry in parallel, which allows for easy testing of alternate or prerelease versions. Each version is given a unique, user-specified suffix, which will be used to create a unique binary name:
pipx install --suffix pipx install --suffix Finally, pipx can install any valid pip requirement spec, which allows for installations of the development version from git , or even for local testing of pull requests:
pipx install --suffix @master git+https://github.com/python-poetry/poetry.git@master pipx install --suffix @pr1234 git+https://github.com/python-poetry/poetry.git@refs/pull/1234/head pipx upgrade poetry pipx uninstall poetry We provide a custom installer that will install Poetry in a new virtual environment and allows Poetry to manage its own environment.
-
Install Poetry The installer script is available directly at install.python-poetry.org, and is developed in its own repository. The script can be executed directly (i.e. ‘curl python’) or downloaded and then executed from disk (e.g. in a CI environment).
The install-poetry.py installer has been deprecated and removed from the Poetry repository. Please migrate from the in-tree version to the standalone version described above.
Linux, macOS, Windows (WSL)
curl -sSL https://install.python-poetry.org Note: On some systems, python may still refer to Python 2 instead of Python 3. We always suggest the python3 binary to avoid ambiguity.
Windows (Powershell)
If you have installed Python through the Microsoft Store, replace py with python in the command above.
- ~/Library/Application Support/pypoetry on MacOS.
- ~/.local/share/pypoetry on Linux/Unix.
- %APPDATA%\pypoetry on Windows.
If you wish to change this, you may define the $POETRY_HOME environment variable:
curl -sSL https://install.python-poetry.org If you want to install prerelease versions, you can do so by passing the --preview option to the installation script or by using the $POETRY_PREVIEW environment variable:
curl -sSL https://install.python-poetry.org Similarly, if you want to install a specific version, you can use --version option or the $POETRY_VERSION environment variable:
curl -sSL https://install.python-poetry.org You can also install Poetry from a git repository by using the --git option:
curl -sSL https://install.python-poetry.org - $HOME/.local/bin on Unix.
- %APPDATA%\Python\Scripts on Windows.
- $POETRY_HOME/bin if $POETRY_HOME is set.
If this directory is not present in your $PATH , you can add it in order to invoke Poetry as poetry .
Alternatively, the full path to the poetry binary can always be used:
- ~/Library/Application Support/pypoetry/venv/bin/poetry on MacOS.
- ~/.local/share/pypoetry/venv/bin/poetry on Linux/Unix.
- %APPDATA%\pypoetry\venv\Scripts\poetry on Windows.
- $POETRY_HOME/venv/bin/poetry if $POETRY_HOME is set.
poetry --version Especially on Windows, self update may be problematic so that a re-install with the installer should be preferred.
poetry self update If you want to install pre-release versions, you can use the --preview option.
poetry self update --preview And finally, if you want to install a specific version, you can pass it as an argument to self update .
poetry self update 1.2.0 Poetry 1.1 series releases are not able to update in-place to 1.2 or newer series releases. To migrate to newer releases, uninstall using your original install method, and then reinstall using the methods above.
curl -sSL https://install.python-poetry.org If you installed using the deprecated get-poetry.py script, you should remove the path it uses manually, e.g.
rm -rf Also remove ~/.poetry/bin from your $PATH in your shell configuration, if it is present.
Poetry can be installed manually using pip and the venv module. By doing so you will essentially perform the steps carried out by the official installer. As this is an advanced installation method, these instructions are Unix-only and omit specific examples such as installing from git .
The variable $VENV_PATH will be used to indicate the path at which the virtual environment was created.
python3 -m venv Poetry will be available at $VENV_PATH/bin/poetry and can be invoked directly or symlinked elsewhere.
To uninstall Poetry, simply delete the entire $VENV_PATH directory.
Unlike development environments, where making use of the latest tools is desirable, in a CI environment reproducibility should be made the priority. Here are some suggestions for installing Poetry in such an environment.
Version pinning
Whatever method you use, it is highly recommended to explicitly control the version of Poetry used, so that you are able to upgrade after performing your own validation. Each install method has a different syntax for setting the version that is used in the following examples.
Using pipx
Just as pipx is a powerful tool for development use, it is equally useful in a CI environment and should be one of your top choices for use of Poetry in CI.
pipx install Using install.python-poetry.org
The official installer script (install.python-poetry.org) offers a streamlined and simplified installation of Poetry, sufficient for developer use or for simple pipelines. However, in a CI environment the other two supported installation methods (pipx and manual) should be seriously considered.
Downloading a copy of the installer script to a place accessible by your CI pipelines (or maintaining a copy of the repository) is strongly suggested, to ensure your pipeline’s stability and to maintain control over what code is executed.
By default, the installer will install to a user-specific directory. In more complex pipelines that may make accessing Poetry difficult (especially in cases like multi-stage container builds). It is highly suggested to make use of $POETRY_HOME when using the official installer in CI, as that way the exact paths can be controlled.
Using pip (aka manually)
For maximum control in your CI environment, installation with pip is fully supported and something you should consider. While this requires more explicit commands and knowledge of Python packaging from you, it in return offers the best debugging experience, and leaves you subject to the fewest external tools.
If you install Poetry via pip , ensure you have Poetry installed into an isolated environment that is not the same as the target environment managed by Poetry. If Poetry and your project are installed into the same environment, Poetry is likely to upgrade or uninstall its own dependencies (causing hard-to-debug and understand errors).
Enable tab completion for Bash, Fish, or Zsh #
poetry supports generating completion scripts for Bash, Fish, and Zsh. See poetry help completions for full details, but the gist is as simple as using one of the following:
Bash #
Auto-loaded (recommended) #
poetry completions bash >> ~/.bash_completion Lazy-loaded #
poetry completions bash >
poetry completions Zsh #
poetry completions zsh > ~/.zfunc/_poetry You must then add the following lines in your ~/.zshrc , if they do not already exist:
Oh My Zsh #
mkdir You must then add poetry to your plugins array in ~/.zshrc :
plugins( poetry . ) prezto #
poetry completions zsh > ~/.zprezto/modules/completion/external/src/_poetry You may need to restart your shell in order for these changes to take effect.
Footer
Python packaging and dependency management made easy.
Documentation
- Introduction
- Basic usage
- Managing dependencies
- Libraries
- Commands
- Configuration
- Repositories
- Managing environments
- Dependency specification
- Plugins
- The pyproject.toml file
- Contributing to Poetry
- Community
- FAQ
- pre-commit hooks
Other Projects
- poetry-core
- install.python-poetry.org
- Bundle plugin
- Export plugin
Copyright © 2018-2023. All Rights Reserved. Powered by
Assignbadges discord как установить
17 авг в 9:54
Автор сообщения: TNX.
Автор сообщения: Raziel
Man, I can make my badge, but it says I was level 1 lol. I'm guessing I lost all my progress because I haven't played in a while?
The level reset was for everyone, it was to replace the new progression system I'm talking about your past level. You're supposed to transfer your old level and display it was a legacy level. Mine says I was level 1, even though I know I was much higher level than that
17 авг в 10:22
Автор сообщения: Raziel
Автор сообщения: TNX.
The level reset was for everyone, it was to replace the new progression system
I'm talking about your past level. You're supposed to transfer your old level and display it was a legacy level. Mine says I was level 1, even though I know I was much higher level than that Same issue, very disappointed right now.
17 авг в 11:11
Автор сообщения: oSecret
Автор сообщения: Raziel
I'm talking about your past level. You're supposed to transfer your old level and display it was a legacy level. Mine says I was level 1, even though I know I was much higher level than that
Same issue, very disappointed right now. Contacted modmail on their discord, you're screwed if you already claimed your legacy badge if you encountered my Issue. In my case, I didn't even know you could contact help to try and get it fixed, as I wanted to actually play the game, so ♥♥♥♥ me I guess for claiming it already. I guess I just don't understand why they can't fix it on their side instead of just making it permanent if you said yes, or maybe idk, give us a "later" button?
17 авг в 11:22
Install GitLab Runner
GitLab Runner runs the CI/CD jobs that are defined in GitLab.
You can install GitLab Runner on your infrastructure, inside a Docker container, or deployed to a Kubernetes cluster.
GitLab Runner is open-source and written in Go. It can run as a single binary and has no language-specific requirements.
After you install GitLab Runner, you must create and register runners with your GitLab instance. This instance can be self-managed, or you can use GitLab.com. You can also follow the tutorial, Create, register, and run your own project runner.
- In a container.
- By downloading a binary manually.
- By using a repository for rpm/deb packages.
- x86, AMD64, ARM64, ARM, s390x, ppc64le
- CentOS, Debian, Ubuntu, RHEL, Fedora, Mint, Oracle, Amazon
- Linux, Windows, macOS, FreeBSD
For security and performance reasons, you should install GitLab Runner on a machine that is separate to the machine that hosts your GitLab instance.
System Requirements
- The anticipated:
- CPU load of CI jobs.
- Memory usage of CI jobs.
- Concurrent CI jobs.
- Projects in active development.
- Developers expected to work in parallel.
FIPS compliant GitLab Runner
In GitLab Runner 14.7 and later, a GitLab Runner binary that is FIPS 140-12 compliant is provided. This binary, built with the Red Hat Go compiler, bypasses the standard library cryptographic routines and instead calls into a FIPS 140-2 validated cryptographic library.
In GitLab Runner 15.1 and later, a UBI-8 minimal is used as the base for creating the GitLab Runner FIPS image.
Only Red Hat Enterprise Linux (RHEL) distributions are supported.
- AMD64
Docker images and RPM packages for the same architectures are also provided.
FIPS compliant GitLab Runner in RHEL
When you use the FIPS version of GitLab Runner in RHEL, you should enable FIPS mode.
FIPS compliant GitLab Runner in other systems and architectures
Refer to this issue to follow progress on adding other architectures and distributions.
Repositories
Binaries
- Install on GNU/Linux
- Install on macOS
- Install on Windows
- Install on FreeBSD
- Install nightly builds
Containers
- Install as a Docker service
- Install on Kubernetes
- Install using the agent for Kubernetes
- Install as GitLab Runner Operator
Autoscale
- Install in autoscaling mode using Docker machine
- Install the registry and cache servers
Help & feedback
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Join First Look to help shape new features.Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.Get Help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).