New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impossible to install extensions #2481
Comments
Yeah, but I'm using the official binaries for Windows, so I'd say it's likely something in your self-compiled build. Can you test any of the contributed Linux binaries from https://ungoogled-software.github.io/ungoogled-chromium-binaries and see whether the problem persists there as well? By "any" I mean either "Linux AppImage 64-bit" or "Portable Linux 64-bit" because only these two are at the v116 version right now. |
I can't. They are compiled with GTK3 at system/package level and GTK3 is exiled from my system at system/package level; i only have it in an isolated directory which i pass to Chromium at compiling and running. I built it with these flags though:
|
Have you forgotten to apply |
If it is in the ungoogled-chromium repository, then no; i clone the repo and systematically apply all patches:
|
Please follow the procedure, otherwise you'll have to solve such issues yourself. |
Now hold on for a moment. If there is a python script for applying the patches, then why did you ask if i forgot to apply a patch? Actually i already "solved" it: i can download the CRX, unpack it and then load it unpacked. But that is rather a workaround. |
OS/Platform
Debian, Ubuntu, and derivatives
Installed
Compiled from source
Version
116.0.5845.111
Have you tested that this is not an upstream issue or an issue with your configuration?
--user-data-dir
command line argument and it could not be reproduced thereDescription
Extension mime handling is unavailable, so it is impossible to install extensions.
How to Reproduce?
Actual behaviour
The mime request handling is disappeared from the flags and the passed flag has no effect.
Expected behaviour
Install the CRX.
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: