* [ISSUE] Chromium @ 2023-05-14 9:12 JuniorSuperTux 2023-05-19 12:20 ` Chromium does not use ~/.config/chromium-flags.conf as arguments JuniorSuperTux 2023-05-19 12:20 ` [ISSUE] [CLOSED] " JuniorSuperTux 0 siblings, 2 replies; 3+ messages in thread From: JuniorSuperTux @ 2023-05-14 9:12 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 825 bytes --] New 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Chromium does not use ~/.config/chromium-flags.conf as arguments 2023-05-14 9:12 [ISSUE] Chromium JuniorSuperTux @ 2023-05-19 12:20 ` JuniorSuperTux 2023-05-19 12:20 ` [ISSUE] [CLOSED] " JuniorSuperTux 1 sibling, 0 replies; 3+ messages in thread From: JuniorSuperTux @ 2023-05-19 12:20 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 197 bytes --] New comment by JuniorSuperTux on void-packages repository https://github.com/void-linux/void-packages/issues/43867#issuecomment-1554491285 Comment: Now that I see this is something arch specific ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ISSUE] [CLOSED] Chromium does not use ~/.config/chromium-flags.conf as arguments 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 1 sibling, 0 replies; 3+ messages in thread From: JuniorSuperTux @ 2023-05-19 12:20 UTC (permalink / raw) To: ml [-- 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-05-19 12:20 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 ` [ISSUE] [CLOSED] " JuniorSuperTux
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).