From: JuniorSuperTux <JuniorSuperTux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Discord should use system-wide electron
Date: Wed, 05 Apr 2023 09:01:14 +0200 [thread overview]
Message-ID: <20230405070114.FWo_w2rOefY0PheUe4GwoQrAo3IiLJmm4nD_XuKYsXs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43280@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
New comment by JuniorSuperTux on void-packages repository
https://github.com/void-linux/void-packages/issues/43280#issuecomment-1497013226
Comment:
Yes, I'm currently using the latest version of the Discord package. Creating ``electron22-flags.conf`` does not seem to make a difference from my current testings. It seems like that opening Discord spawns a XWayland process, which from my understanding is an emulation of Xorg. Killing the process kills the Discord instance. The Discord process does not seem to have the arguments either. Or could it be possible that it's normal behavior?
next prev parent reply other threads:[~2023-04-05 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 3:42 [ISSUE] " JuniorSuperTux
2023-04-05 4:44 ` 0x5c
2023-04-05 7:01 ` JuniorSuperTux [this message]
2023-04-05 8:22 ` classabbyamp
2023-04-05 12:20 ` JuniorSuperTux
2023-04-05 12:21 ` JuniorSuperTux
2023-04-06 3:55 ` 0x5c
2023-04-06 11:54 ` JuniorSuperTux
2023-04-09 14:12 ` JuniorSuperTux
2023-04-10 14:20 ` JuniorSuperTux
2023-04-10 14:24 ` JuniorSuperTux
2023-04-10 15:40 ` Discord does not respect electron-flags.conf paper42
2023-04-11 5:31 ` [ISSUE] [CLOSED] " classabbyamp
2023-04-11 5:31 ` classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230405070114.FWo_w2rOefY0PheUe4GwoQrAo3IiLJmm4nD_XuKYsXs@z \
--to=juniorsupertux@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).