ungoogled-chromium

I can't believe I'm actually writing this from www/netsurf with JavaScript disabled right now (though I'm still on Arch Linux preparing myself for a first FreeBSD installation attempt on my laptop).

I think for looking up some light stuff like documentation this is quite a reasonable solution, but of course no replacement for doing mainstream things that require a password manager, spelling correction and the usual web nonsense.
 
Heh, well I am reading your post on netsurf myself. Its reads loud and clear :)

I am trying to cut down on things that overly consume browser features anyway. So netsurf is very reasonable for my uses (but one that I unfortunately can't always recommend for others with different browsing habits).
The only reason I really have to keep a backup browser is for dreaded internet banking. Those things are terrible!

If I keep entirely to those sites, it remains reasonably safe. However the banking website are so overly bloated that I simply cannot see them being secure.
 
MasterOne said:
Is anybody interested in creating a port for this (preferably with libva support for HW accelerated video)?
There is an open issue for adding FreeBSD support but that hasn't found more interest since 2016, though I'm confident that @Eloston is willing to provide support if any questions arise.

Regular Chromium just doesn't cut it privacy-wise and I don't see the point in the many Chromium clones except that one project that just removes anything Google, resulting in a plain Chromium without all the nasty stuff. I know that there is Iridium browser in ports, but that one gets updated quite infrequent (so I'm concerned about possible security issues) and since ungoogled-chromium lists Iridium browser as one of the sources for borrowed features it's just not the same.

P.S. I would (try to create a port for it) if I could, but I'm not a programmer or developer but just a user. I'm currently still on Arch Linux, but I think I want to try with FreeBSD after quite some time on my laptop again.
Click to expand...
Not yet in the ports tree, but according to this page there's some recent activity:

github.com

Add FreeBSD support · Issue #121 · ungoogled-software/ungoogled-chromium

Could you provide support for freebsd platforms and android or cooperhead (security gardened android) https://copperhead.co/android/
github.com github.com

and a binary is available here (which I was curious to try):


Spoiler alert...it works.

Code: 
$ mkdir -p $HOME/bin/ungoogled-chromium
$ cd $HOME/bin/ungoogled-chromium
$ tar xvf ~/Downloads/ungoogled-chromium-100.0.4896.88.pkg
$ cd

To avoid clobbering the chromium profile if you have one, invoke as:

Code: 
$ $HOME/bin/ungoogled-chromium/usr/local/share/ungoogled-chromium/chrome-wrapper --user-data-dir=$HOME/.config/ungoogled-chromium

(otherwise the profile will default to $HOME/.config/chromium).

Extensions can be installed/updated using:

github.com

GitHub - NeverDecaf/chromium-web-store: Allows adding extensions from chrome web store on ungoogled-chromium. Also adds semi-automatic extension updating.

Allows adding extensions from chrome web store on ungoogled-chromium. Also adds semi-automatic extension updating. - NeverDecaf/chromium-web-store
github.com github.com

NB - for this to work, go to "chrome://flags", search for #extension-mime-request-handling and set it to "Always prompt for install".

Edit: typo
 
rootbert said:
what's the difference to www/iridium?
Click to expand...
Iridium goes through a process where code embedded URL's are replaced with an Iridium URL. The code is then tested to see what information is being harvested. As you can imagine, this process requires some time and historically, cannot keep up with all the Chromium releases. Ungoogled chromium harvests patches from Iridium, Inox, Debian and Bromite.
See "Borrowed Features" at github:
https://github.com/Eloston/ungoogled-chromium

Ungoogled chromium is usually no more than a week or 2 behind upstream. Also, Ungoogled-Chromium provides arm/arm64 android builds.
 
Thanks for the heads-up. I had just been using the FreeBSD binary from the github downloads page so far. Have just installed from the pkg repo. One minor "gotcha" I discovered is that to run it via the wrapper script I had to edit the last line in /usr/local/share/ungoogled-chromium/chrome-wrapper:

Code: 
#exec $CMD_PREFIX "$HERE/chrome" "$@"
exec $CMD_PREFIX "$HERE/ungoogled-chromium" "$@"

so that the exec line refers to ungoogled-chromium instead of chrome.
 
Does anyone know how to set ungoogled-chromium as the default browser? The "Make Default" option doesn't work, or if it does, it's lost after a reboot or upgrade.
 
mfoacs said:
Does anyone know how to set ungoogled-chromium as the default browser? The "Make Default" option doesn't work, or if it does, it's lost after a reboot or upgrade.
Click to expand...
That depends on your system setup/configuration.
"Default applications" are not handled by FreeBSD. Look for the corresponding documentation of whatever session manager / DE you're using.
 
mfoacs said:
Does anyone know how to set ungoogled-chromium as the default browser? The "Make Default" option doesn't work, or if it does, it's lost after a reboot or upgrade.
Click to expand...
Add the following code to the ~/.config/mimeapps.list file (under the [Default Applications] section):

text/html=chromium-browser.desktop
 
dostoievsky said:
Hello. It is said that
www/chromium uses sndio by default.

does ungoogled-chromium does the same?
How could I check that?
Click to expand...
Hi. There are port configuration options on FreshPorts set by default and i can see that some of them are "on" by default.
1726781205479.png

I also have ungoogled-chromium installed and i can run pkg info ungoogled-chromium to see which options are present on the package.
 

Attachments

  • 1726781262003.png
    1726781262003.png
    89.6 KB · Views: 39
dostoievsky said:
Hello. It is said that
www/chromium uses sndio by default.

does ungoogled-chromium does the same?
How could I check that?
Click to expand...

AFAIK www/chromium and www/ungoogled-chromium try to use the audio backends in the following order by default: pulseaudio, sndio, alsa. At least that's what I read from PR 246449.

You can set one of these backends explicitely on the chrome://flags site (just type this in your URL) under the Audio Backend section.
 
Since when I tryed to mess with

to configure virtual oss to use diferent devices for input/output, the whole chrome ecosystem got messed.
Video playback dosent work more, as well audio in/out.

Over firefox, everything works fine, as well audacity with OSS host

I did disabled virtual_oss and reboot and yeah, video playback starts working again.
And audio only work with a single default device.

Man, I thought once that configure networking and bhyve was hard, but this is hell.

EDIT:

I switched to pulseaudio as backend, and now I can select diferent devices when using conference apps (meet, discord, etc) but I could not get audio over youtube.

EDIT2:

I was the one to fault, because I was messing with
virtual_oss_cmd /dev/vdsp.ctl -f /dev/dsp without knowing what it was for.
 
dostoievsky said:
Since when I tryed to mess with

to configure virtual oss to use diferent devices for input/output, the whole chrome ecosystem got messed.
Video playback dosent work more, as well audio in/out.

Over firefox, everything works fine, as well audacity with OSS host
Click to expand...

It seems there's no way to tell chromium which sndio device descriptor to use, so I guess it uses the default device descriptor. This is an "alias" to the /dev/dsp audio device, which itself acts like a symlink to your default audio device /dev/dspX (see sysctl hw.snd.default_unit).

So in order for chromium to work with audio/virtual_oss and sndio, you need to create an OSS audio device with the name dsp when starting virtual_oss, this is accomplished with the -d flag (see virtual_oss(8), but this is also mentioned in the wiki entry).

How did you start virtual_oss? Maybe also show the output of cat /dev/sndstat.
 
bsdcode, thank you for helping me. I just really was doing things wrong. After creating my device I was setting
virtual_oss_cmd /dev/vdsp.ctl -f /dev/dsp command without really knowing what it was for. That ended messing up with chromium playback somehow. Since it inst an browser issue, I think here isnt really the place to keep the issue, and I am the one at fault, lol. I very thanks you and monwarez over discord for helping me out, and nxjoseph as well for the tip.
 
dostoievsky said:
bsdcode, thank you for helping me. I just really was doing things wrong. After creating my device I was setting
virtual_oss_cmd /dev/vdsp.ctl -f /dev/dsp command without really knowing what it was for. That ended messing up with chromium playback somehow. Since it inst an browser issue, I think here isnt really the place to keep the issue, and I am the one at fault, lol. I very thanks you and monwarez over discord for helping me out, and nxjoseph as well for the tip.
Click to expand...

No problem, it's always nice to help people out.

dostoievsky said:
Man, I thought once that configure networking and bhyve was hard, but this is hell.
Click to expand...

I think the world would be a better place if everyone just uses OSS. But alas, we are obviously living in the borked timeline where OSSv4 became proprietary in 2002 and the whole "audio backend business" went downhill from there...
 
You must log in or register to reply here.
Back
Top