Iridium browser install issue

[Huckleberry Finn]

You can stop the keyring nonsense by editing the launcher command to read “%U --password-store=basic” at the end (no quote marks).

Thank you :)

[colin_b]

I watched Google Chrome [no addons] vs Iridium Browser [addons] https://www.youtube.com/watch?v=NgPFXbl3QbU and I was stunned at how much data the Chrome browser spews out to third parties as it is used.

I use Firefox, but I was curious how Iridium compared to it, so I downloaded it from the stable repo of the MXPI.

I had the same problem as the OP - when I found it in the whisker menu and selected it nothing happened. A bit of head scratching led me to this forum post, and the hack detailed earlier works - thanks

Is there a problem with the install that can be fixed?

Code: Select all

System:    Host: Colin Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: Gigabyte product: B450 AORUS PRO v: N/A serial: <filter> 
           Mobo: Gigabyte model: B450 AORUS PRO-CF v: x.x serial: <filter> 
           UEFI: American Megatrends v: F4 date: 01/08/2019 
CPU:       Topology: Quad Core model: AMD Ryzen 5 2400GE with Radeon Vega Graphics bits: 64 
           type: MT MCP arch: Zen L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 51104 
           Speed: 1596 MHz min/max: 1600/3200 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1595 
           4: 1589 5: 1594 6: 1594 7: 1595 8: 1587 
Graphics:  Device-1: AMD vendor: Gigabyte driver: amdgpu v: kernel bus ID: 06:00.0 
           Display: x11 server: X.Org 1.19.2 driver: none resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD RAVEN (DRM 3.27.0 4.19.0-5-amd64 LLVM 7.0.0) v: 4.5 Mesa 18.2.6 
           direct render: Yes 
Audio:     Device-1: AMD driver: snd_hda_intel v: kernel bus ID: 06:00.1 
           Device-2: AMD vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 06:00.6 
           Sound Server: ALSA v: k4.19.0-5-amd64 
Network:   Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: 5.4.0-k 
           port: f000 bus ID: 03:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 191.43 GiB (41.1%) 
           ID-1: /dev/sda vendor: Seagate model: ST500LM000-1EJ162 size: 465.76 GiB 
Partition: ID-1: / size: 190.29 GiB used: 12.95 GiB (6.8%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 40.1 C mobo: N/A gpu: amdgpu temp: 40 C 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.uk.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.uk.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 299 Uptime: 1d 21h 19m Memory: 13.71 GiB used: 5.70 GiB (41.6%) 
           Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33 

With regard to the Iridium browser itself, it is consiberably faster than FF at rendering pages on my humble 2.5Mbps connection. Very impressed.

[Stevo]

We do have the newer version in the experimental MX 17/18 repo, because it needs a minimum of a gcc-7 runtime library that's in there too (as well as gcc-8). http://mxrepo.com/mx/experimental/pool/ ... m-browser/

It's in the main MX 19 repo.

I think the sandbox is considered a feature. it does work "as is" with Liquorix kernels.

[ASL]

MX 19_x64 here. Same problem, same solution as above. Talk about mystery line :)

[fehlix]

MX 19_x64 here. Same problem, same solution as above. Talk about mystery line :)

There have been a couple of "problems" mentioned in this thread. What "solution" did you apply to solve what "problem"?

[ASL]

Oh, sorry. I couldn't get the Iridium browser to start. Then I added the fix:

Code: Select all

echo kernel.unprivileged_userns_clone=1 | sudo   tee  /etc/sysctl.d/00-local-userns.conf

And now it works. I found out later that the fix actually came from the Iridium download page:
https://iridiumbrowser.de/downloads/debian
Where they say it is a problem that appears in several Debian distros.