Skip to content

Commit

Permalink
update with trivalent naming
Browse files Browse the repository at this point in the history
  • Loading branch information
RoyalOughtness authored Jan 7, 2025
1 parent 83e0545 commit 56db4a8
Show file tree
Hide file tree
Showing 5 changed files with 14 additions and 14 deletions.
16 changes: 8 additions & 8 deletions docs/FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,24 +129,24 @@ mkdir -p ~/.config/environment.d && echo "GSK_RENDERER=gl" >> ~/.config/environm

This should no longer be required as of F41: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/42

#### Why won't `hardened-chromium` start?
#### Why won't `trivalent-browser` start?

Try starting `hardened-chromium` from the commandline by running `hardened-chromium`. If you get an error about the current profile already running on another device, this is an issue with upstream chromium which can happen when you `rpm-ostree update` or `rpm-ostree rebase`. To fix this, simply run `rm ~/.config/chromium/SingletonLock`.
Try starting `trivalent-browser` from the commandline by running `trivalent-browser`. If you get an error about the current profile already running on another device, this is an issue with upstream chromium which can happen when you `rpm-ostree update` or `rpm-ostree rebase`. To fix this, simply run `rm ~/.config/chromium/SingletonLock`.
\
\
`bubblejail` ***SHOULD NOT*** be used on `hardened-chromium`, there are issues reported with the pairing and removing the `bubblejail` config after it is applied can be difficult. It should also be noted that applying additional sandboxing may interfere with chromium's own internal sandbox, so it can end up reducing security.
`bubblejail` ***SHOULD NOT*** be used on `trivalent-browser`, there are issues reported with the pairing and removing the `bubblejail` config after it is applied can be difficult. It should also be noted that applying additional sandboxing may interfere with chromium's own internal sandbox, so it can end up reducing security.

#### Why won't `hardened-chromium` start on Nvidia?
#### Why won't `trivalent-browser` start on Nvidia?

On some Nvidia machines, `hardened-chromium` defaults to the X11 backend. Since secureblue disables Xwayland by default, this means that you will need to run `ujust toggle-xwayland` and reboot, for `hardened-chromium` to work.
On some Nvidia machines, `trivalent-browser` defaults to the X11 backend. Since secureblue disables Xwayland by default, this means that you will need to run `ujust toggle-xwayland` and reboot, for `trivalent-browser` to work.

#### Why don't some websites that require JIT/WebAssembly work in hardened-chromium even with the V8 Optimizer toggle enabled?
#### Why don't some websites that require JIT/WebAssembly work in trivalent-browser even with the V8 Optimizer toggle enabled?

This is an [upstream bug](https://issues.chromium.org/issues/373893056) that prevents V8 optimization settings from being applied to iframes embedded within a parent website. As a result, WebAssembly may not function on services that use a separate URL for their content delivery network or other included domains, such as VSCode Web (https://github.dev). To make VSCode Web work properly, you need to manually allow V8 optimizations for the CDN by adding `https://[*.]vscode-cdn.net` to your list of trusted websites.

#### Why don't extensions work in `hardened-chromium`?
#### Why don't extensions work in `trivalent-browser`?

Extensions in `hardened-chromium` are disabled by default, for security reasons it is not advised to use them. If you want content/ad blocking, that is already built into `hardened-chromium` and enabled by default. If you require extensions, you can re-enable them by disabling the `Disable Extensions` toggle under `chrome://settings/security`, then restart your browser (this toggle is per-profile).
Extensions in `trivalent-browser` are disabled by default, for security reasons it is not advised to use them. If you want content/ad blocking, that is already built into `trivalent-browser` and enabled by default. If you require extensions, you can re-enable them by disabling the `Disable Extensions` toggle under `chrome://settings/security`, then restart your browser (this toggle is per-profile).
\
\
If the extension you installed doesn't work, it is likely because it requires WebAssembly (WASM) for some cryptographic library or some other optimizations (this is the case with the Bitwarden extension). To re-enable JavaScript JIT and WASM for extensions, enable the feature `chrome://flags/#internal-page-jit`.
2 changes: 1 addition & 1 deletion files/gschema-overrides/zz1-secureblue.gschema.override
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@

[org.gnome.shell]
allow-extension-installation=false
favorite-apps = ['hardened-chromium.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Ptyxis.desktop', 'com.github.tchx84.Flatseal.desktop', 'io.github.flattool.Warehouse.desktop']
favorite-apps = ['trivalent-browser.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Ptyxis.desktop', 'com.github.tchx84.Flatseal.desktop', 'io.github.flattool.Warehouse.desktop']
enabled-extensions = []

[org.gnome.desktop.interface]
Expand Down
2 changes: 1 addition & 1 deletion files/scripts/addchromiumdesktopfile.sh
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@
# Tell build process to exit if there are any errors.
set -oue pipefail

sed -i 's/org.mozilla.firefox/hardened-chromium/' /usr/share/wayfire/wf-shell.ini
sed -i 's/org.mozilla.firefox/trivalent-browser/' /usr/share/wayfire/wf-shell.ini
6 changes: 3 additions & 3 deletions files/scripts/selinux/chromium/chromium.fc
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
/usr/lib/chromium-browser/chromium-browser -- gen_context(system_u:object_r:chromium_exec_t,s0)
/usr/lib/chromium-browser/chrome_crashpad_handler -- gen_context(system_u:object_r:chromium_exec_t,s0)
/usr/lib/chromium-browser/chromium-browser.sh -- gen_context(system_u:object_r:chromium_exec_t,s0)
/usr/lib/hardened-chromium/hardened-chromium -- gen_context(system_u:object_r:chromium_exec_t,s0)
/usr/lib/hardened-chromium/chrome_crashpad_handler -- gen_context(system_u:object_r:chromium_exec_t,s0)
/usr/lib/hardened-chromium/hardened-chromium.sh -- gen_context(system_u:object_r:chromium_exec_t,s0)
/usr/lib/trivalent-browser/trivalent-browser -- gen_context(system_u:object_r:chromium_exec_t,s0)
/usr/lib/trivalent-browser/chrome_crashpad_handler -- gen_context(system_u:object_r:chromium_exec_t,s0)
/usr/lib/trivalent-browser/trivalent-browser.sh -- gen_context(system_u:object_r:chromium_exec_t,s0)
2 changes: 1 addition & 1 deletion files/scripts/selinux/chromium/chromium.sh
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,4 @@ make -f /usr/share/selinux/devel/Makefile chromium.pp || exit
/usr/sbin/semodule -i chromium.pp

/sbin/restorecon -F -R -v /usr/lib/chromium-browser/
/sbin/restorecon -F -R -v /usr/lib/hardened-chromium/
/sbin/restorecon -F -R -v /usr/lib/trivalent-browser/

0 comments on commit 56db4a8

Please sign in to comment.