Github messages for voidlinux
 help / color / mirror / Atom feed
From: JuniorSuperTux <JuniorSuperTux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Chromium does not use ~/.config/chromium-flags.conf as arguments
Date: Fri, 19 May 2023 14:20:54 +0200	[thread overview]
Message-ID: <20230519122054.3SgJ3O8iGtfzRtsBCrqMUqFD-xYsup_TN7z_G7DcqoU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43867@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

Closed issue by JuniorSuperTux on void-packages repository

https://github.com/void-linux/void-packages/issues/43867

Description:
### Is this a new report?

Yes

### System Info

 Void 6.1.27_1 x86_64 GenuineIntel uptodate rrmFFFFFFFFFFFFFFFF

### Package(s) Affected

chromium-113.0.5672.63_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Chromium uses the content in ``~/.config/chromium-flags.conf`` or the ``$CHROMIUM_FLAGS`` environment variable as arguments.

### Actual behaviour

Chromium does not read any of those above.

Every Electron apps also don't use ``~/.config/electron-flags.conf``

### Steps to reproduce

1. Add the desired arguments to ``$CHROMIUM_FLAGS`` or ``~/.config/chromium-flags.conf``
2. Nothing happens

      parent reply	other threads:[~2023-05-19 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14  9:12 [ISSUE] Chromium JuniorSuperTux
2023-05-19 12:20 ` Chromium does not use ~/.config/chromium-flags.conf as arguments JuniorSuperTux
2023-05-19 12:20 ` JuniorSuperTux [this message]

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=20230519122054.3SgJ3O8iGtfzRtsBCrqMUqFD-xYsup_TN7z_G7DcqoU@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).