From: Jorge P. de Morais Neto via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Marius Bakke <marius@gnu.org>, Leo Famulari <leo@famulari.name>
Cc: 49029@debbugs.gnu.org
Subject: bug#49029: ungoogled-chromium failed to disable malware extension The Great Suspender
Date: Wed, 16 Jun 2021 19:17:13 -0300 [thread overview]
Message-ID: <871r91e9p2.fsf@disroot.org> (raw)
In-Reply-To: <878s39ms8w.fsf@gnu.org>
Hi Marius.
Em [2021-06-16 qua 23:09:19+0200], Marius Bakke escreveu:
> It's not easily possible to install extensions with ungoogled-chromium,
> apart from the two that are available directly through Guix. If the
> user goes out of their way to install extensions, such as using a
> browser from a different distro, there is little we can do.
>
> Mixing browser profiles between the vanilla and ungoogled Chromium is
> not a supported use case. Warranty void.
In my case, the Debian Chromium's profile was already there when I
installed Guix's ungoogled-chromium. I didn't even notice that Guix's
ungoogled-chromium cannot install extensions from the Chrome Store.
> I'd accept a patch that warns or refuses to use a "tainted" browser
> profile, or changes the default browser profile directory so it does not
> conflict with vanilla.
Unfortunately I cannot write such a patch; I would have to dedicate a
large amount of time learning about Chromium's insides (which are
reportedly byzantine) and I don't even know if I'll actually keep using
Guix's ungoogled-chromium. But couldn't you report this to
ungoogled-chromium upstream?
> But I'm inclined to close this as "not-a-bug" for now. WDYT, Jorge?
In my humble opinion, users should be communicated, especially users of
Guix package manager on another GNU distribution. Maybe at least a
warning in the package description that mixing Guix's ungoogled-chromium
and host distribution's Chromium on the same profile is unsupported?
Regards
--
- https://stallmansupport.org "In Support of Richard Stallman"
- I am Brazilian. I hope my English is correct and I welcome feedback.
- https://www.defectivebydesign.org
- https://www.gnu.org
next prev parent reply other threads:[~2021-06-16 22:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 21:29 bug#49029: ungoogled-chromium failed to disable malware extension The Great Suspender Jorge P. de Morais Neto via Bug reports for GNU Guix
2021-06-15 13:49 ` Leo Famulari
2021-06-15 14:40 ` Leo Prikler
2021-06-15 16:59 ` Jorge P. de Morais Neto via Bug reports for GNU Guix
2021-06-16 16:31 ` Leo Famulari
2021-06-16 16:33 ` Leo Famulari
2021-06-16 21:09 ` Marius Bakke
2021-06-16 22:17 ` Jorge P. de Morais Neto via Bug reports for GNU Guix [this message]
2022-01-04 4:55 ` Maxim Cournoyer
2022-01-06 11:34 ` Jorge P. de Morais Neto via Bug reports for GNU Guix
2022-01-06 13:46 ` Maxim Cournoyer
2022-01-07 0:09 ` Jorge P. de Morais Neto via Bug reports for GNU Guix
2022-01-07 18:09 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871r91e9p2.fsf@disroot.org \
--to=bug-guix@gnu.org \
--cc=49029@debbugs.gnu.org \
--cc=jorge+list@disroot.org \
--cc=leo@famulari.name \
--cc=marius@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).