Page 1 of 1
Iridium browser install issue
Posted: Fri Aug 16, 2019 7:01 am
by ChrisBE
JayM wrote: Thu Aug 08, 2019 11:26 pm
Iridium is available in the MX Stable repository. You should really install that using MX Package Installer (MXPI) rather than downloading something from the Internet and installing that. Make sure that nothing else that uses apt (Synaptic or the MX Updater) is running at the same time or you'll get those errors when trying to install Iridium because MXPI can't get an exclusive lock on apt.
Hi, 1st time user, trying linux again after 20 yrs, I had tried several distro's back in 1998 or so. [Win 10 user, also here on win10 because the live USB doensn't recognize my AZERTY keyboard (choosing Belgian doesn't work).

]
I installed Iridium browser from the MXPI. I can see the app, clicking on it however, doesn't do a thing.
I'm running the demo on a antiX live USB. Could this be the problem?
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 9:38 am
by fehlix
ChrisBE wrote: Fri Aug 16, 2019 7:01 am
... because the live USB doensn't recognize my AZERTY keyboard (choosing Belgian doesn't work).
Re-keyboard: The simpelst way to re-select keyboard or language running MX Linux , e.g. on a live-usb would be to just logout and select on the login-screen on the upper right corner keyboard and/or lang.
(Default username/pass : demo/demo )
Also you can press F3 to see the selected keyboad on the screen:
select-keyboard-lang-at-login.png
show-keyboard-with-F3-at-login.png
PS: Welcome to the Forum!
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 9:58 am
by fehlix
ChrisBE wrote: Fri Aug 16, 2019 7:01 am
I'm running the demo on a antiX live USB. Could this be the problem?
You might try also latest MX Linux MX-18.3-July ISO.
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 12:28 pm
by ChrisBE
fehlix wrote: Fri Aug 16, 2019 9:38 am
ChrisBE wrote: Fri Aug 16, 2019 7:01 am
... because the live USB doensn't recognize my AZERTY keyboard (choosing Belgian doesn't work).
Re-keyboard: The simpelst way to re-select keyboard or language running MX Linux , e.g. on a live-usb would be to just logout and select on the login-screen on the upper right corner keyboard and/or lang.
(Default username/pass : demo/demo )
Also you can press F3 to see the selected keyboad on the screen:
select-keyboard-lang-at-login.png
show-keyboard-with-F3-at-login.png
PS: Welcome to the Forum!
Thx for welcoming me, and especially for your kind and quick reply! This worked perfectly!

Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 12:41 pm
by ChrisBE
fehlix wrote: Fri Aug 16, 2019 9:58 am
ChrisBE wrote: Fri Aug 16, 2019 7:01 am
I'm running the demo on a antiX live USB. Could this be the problem?
You might try also latest MX Linux MX-18.3-July ISO.
I installed this (the latest) version a week ago. Iso > Rufus > bootable USB (I'm on it now). I tried again, same problem: nothing happens.

Perhaps I need to install MXLinux from the liveUSB to another device, I hope it'll work.
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 1:00 pm
by fehlix
ChrisBE wrote: Fri Aug 16, 2019 12:41 pm
I installed this (the latest) version a week ago. Iso > Rufus > bootable USB (I'm on it now). I tried again, same problem: nothing happens.

Perhaps I need to install MXLinux from the liveUSB to another device, I hope it'll work.
Nope, that's a chromium-sanbox based issue, where they changed something recently...:
Open terminal as normale user and run this from command line :
Code: Select all
sudo sysctl -w kernel.unprivileged_userns_clone=1
Start the browser and see how it goes.
To get it permanently enabled run:
Code: Select all
echo kernel.unprivileged_userns_clone=1 | sudo tee /etc/sysctl.d/00-local-userns.conf
HTH

EDIT: fixed a typo : missing space after the "tee"
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 1:24 pm
by Stevo
The latest Iridium for MX 17 is in the experimental repository, because it needs gcc-8 to compile and run, and that's currently in experimental. That Iridium is in the main MX 19 repo, though.
We have another modern compiler, clang-7, in our main repo, that Iridium might build with instead of gcc-8, but I have to confess that I don't know the procedure to switch a Debian build over from gcc to clang, and Googling that doesn't result in much.
Some apps, such as Telegram 1.7.0, need gcc-8 to build, but not to run, so we can have those in our test repository.
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 1:26 pm
by fehlix
Stevo wrote: Fri Aug 16, 2019 1:24 pm
The latest Iridium for MX 17 is in the experimental repository, because it needs gcc-8 to compile and run, and that's currently in experimental. That Iridium is in the main MX 19 repo, though.
Does it run without the userns-hack?
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 1:30 pm
by Stevo
fehlix wrote: Fri Aug 16, 2019 1:26 pm
Stevo wrote: Fri Aug 16, 2019 1:24 pm
The latest Iridium for MX 17 is in the experimental repository, because it needs gcc-8 to compile and run, and that's currently in experimental. That Iridium is in the main MX 19 repo, though.
Does it run without the userns-hack?
Ummm...what's that? Is it the sandbox workaround? If so, I think it still needs it on the Debian-type kernels, though the Liquorix kernels don't need that.
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 1:43 pm
by fehlix
Stevo wrote: Fri Aug 16, 2019 1:30 pm
fehlix wrote: Fri Aug 16, 2019 1:26 pm
Stevo wrote: Fri Aug 16, 2019 1:24 pm
The latest Iridium for MX 17 is in the experimental repository, because it needs gcc-8 to compile and run, and that's currently in experimental. That Iridium is in the main MX 19 repo, though.
Does it run without the userns-hack?
Ummm...what's that? Is it the sandbox workaround? If so, I think it still needs it on the Debian-type kernels, though the Liquorix kernels don't need that.
Yep, some chromium-sandbox mystic - made recently mandatory:
Does it run without the userns-"fix?
Check:
Code: Select all
$ sudo sysctl kernel.unprivileged_userns_clone
kernel.unprivileged_userns_clone = 0
Run:
Code: Select all
$ iridium-browser
Using PPAPI flash.
[30139:30139:0816/193346.928524:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x558405490f69 <unknown>
#1 0x5584053d2ac3 <unknown>
#2 0x5584053e8e9e <unknown>
#3 0x558406a73579 <unknown>
#4 0x558404d5fc82 <unknown>
#5 0x558404d6835f <unknown>
#6 0x558404d5e4e1 <unknown>
#7 0x55840272c843 ChromeMain
#8 0x7f8547d7c09b __libc_start_main
#9 0x55840272c6fa _start
Received signal 6
#0 0x558405490f69 <unknown>
#1 0x5584053d2ac3 <unknown>
#2 0x558405490ae1 <unknown>
#3 0x7f854a3dd730 <unknown>
#4 0x7f8547d8f7bb gsignal
#5 0x7f8547d7a535 abort
#6 0x55840548f925 <unknown>
#7 0x5584053e926d <unknown>
#8 0x558406a73579 <unknown>
#9 0x558404d5fc82 <unknown>
#10 0x558404d6835f <unknown>
#11 0x558404d5e4e1 <unknown>
#12 0x55840272c843 ChromeMain
#13 0x7f8547d7c09b __libc_start_main
#14 0x55840272c6fa _start
r8: 0000000000000000 r9: 00007ffeafc1eab0 r10: 0000000000000008 r11: 0000000000000246
r12: 00007ffeafc1f728 r13: 000000000000016d r14: 00007ffeafc1ed50 r15: 00007ffeafc1f720
di: 0000000000000002 si: 00007ffeafc1eab0 bp: 00007ffeafc1ed00 bx: 0000000000000006
dx: 0000000000000000 ax: 0000000000000000 cx: 00007f8547d8f7bb sp: 00007ffeafc1eab0
ip: 00007f8547d8f7bb efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
demo@mx1:~/Desktop
Fix:
Code: Select all
$ sudo sysctl -w kernel.unprivileged_userns_clone=1
kernel.unprivileged_userns_clone = 1
Run:
Code: Select all
$ iridium-browser
Using PPAPI flash.
[30261:30261:0816/193429.652083:ERROR:browser_dm_token_storage_linux.cc(101)] Error: /etc/machine-id contains 0 characters (32 were expected).
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
[30291:30291:0816/193429.686387:ERROR:vaapi_wrapper.cc(324)] vaInitialize failed (ignore if using Wayland desktop environment): unknown libva error
[30291:30291:0816/193429.686463:ERROR:vaapi_wrapper.cc(327)] Could not get a valid DRM VA display
*** autoupdate was enabled, overriding with false
** Message: 19:34:33.829: Remote error from secret service: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.Secret.Collection” on object at path /org/freedesktop/secrets/collection/login
So it runs but only with the "kernel.unprivileged_userns_clone" -fix/hack, except one would use the no-sandbox flag
Code: Select all
iridium-browser -version
Using PPAPI flash.
Iridium 2019.04 Built on Debian 10, running on MX 19

Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 2:02 pm
by Stevo
Yes...I was also able to get the vaapi messages to go away by making sure that va-api was working for my Intel GPU, raising my hopes that it would be able to show embedded web video using va-api, (4K Youtube video with practically no extra CPU use!), but it didn't work right off. But now that I think about it, I don't remember going into the settings and enabling the acceleration, which is required, so I'll have to try that before writing acceleration off.
Iridium source is taken right from the va-api enabled PPA for Chromium:
https://www.linuxuprising.com/2018/08/h ... rated.html
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 2:06 pm
by anticapitalista
You do realise O/P is using antiX?
Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 2:15 pm
by fehlix
anticapitalista wrote: Fri Aug 16, 2019 2:06 pm
You do realise O/P is using antiX?
in post #5, OP tried it in MX Linux
[SOLVED] Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 3:51 pm
by ChrisBE
fehlix wrote: Fri Aug 16, 2019 1:00 pm
ChrisBE wrote: Fri Aug 16, 2019 12:41 pm
I installed this (the latest) version a week ago. Iso > Rufus > bootable USB (I'm on it now). I tried again, same problem: nothing happens.

Perhaps I need to install MXLinux from the liveUSB to another device, I hope it'll work.
Nope, that's a chromium-sanbox based issue, where they changed something recently...:
Open terminal as normale user and run this from command line :
Code: Select all
sudo sysctl -w kernel.unprivileged_userns_clone=1
Start the browser and see how it goes.
To get it permanently enabled run:
Code: Select all
echo kernel.unprivileged_userns_clone=1 | sudo tee /etc/sysctl.d/00-local-userns.conf
HTH

EDIT: fixed a typo : missing space after the "tee"
Guess on which browser I am now?
Iridium! It's not so polished as the windows version, but it's one of the most secure browers out there. I didn't understand the code you wrote for the terminal, but THANK YOU so much for fixing the problem, great support here, you're a genius!

Re: Iridium browser install issue
Posted: Fri Aug 16, 2019 4:43 pm
by fehlix
ChrisBE wrote: Fri Aug 16, 2019 3:51 pm
.. but it's one of the most secure browers out there.
... I didn't understand the code ...
Great that it works ...perhaps might to look to it to use it. Thank's for the hint.
... I don't understand the code either

Re: Iridium browser install issue
Posted: Sat Aug 17, 2019 1:17 pm
by ChrisBE
fehlix wrote: Fri Aug 16, 2019 4:43 pm
Great that it works ...perhaps might to look to it to use it. Thank's for the hint.
... I don't understand the code either
LOL
In Iridium there's only 1 thing to be unchecked, see
https://spyware.neocities.org/guides/iridium.html - go OFFline first. Then, spyware is zero.
I use Iridium with specific extensions, see
https://digdeeper.neocities.org/ghost/addons.html, uMatrix rocks.
And of course with a beautiful theme

Oh, and I use Swisscows as search engine.
Addition 18/08/19 - Some linux users 'warned' me about Iridium, saying that it's possible a small project and that users should stick to Chromium browser etc.
Re: Iridium browser install issue
Posted: Sat Aug 17, 2019 2:00 pm
by Huckleberry Finn
ChrisBE wrote: Fri Aug 16, 2019 3:51 pm
Guess on which browser I am now?
Iridium!
So, it seems you're gonna mark the thread as [SOLVED] ?
Re: Iridium browser install issue
Posted: Sun Aug 18, 2019 6:23 am
by ChrisBE
Huckleberry wrote: Sat Aug 17, 2019 2:00 pm
So, it seems you're gonna mark the thread as [SOLVED] ?
Marked. I hope I did it right. (I had to search for it, I'm not use to do this on a forum, so...). Thx for the hint and again many thx for the great support here.

Re: Iridium browser install issue
Posted: Sun Aug 18, 2019 7:16 am
by Huckleberry Finn
ChrisBE wrote: Sun Aug 18, 2019 6:23 am
Marked. I hope I did it right.

Errr... it still looks unmarked. Just need to do this: go to your
first post in this thread and click the pencil icon (
edit) and add [SOLVED] at the beginning of the
title.
By the way, glad you've solved the issue.
Meanwhile, I like also the Iridium and installed on the other 64bit laptop (by the way, I wish it was for 32 bits also), but it began displaying "keyring blah blah" and I quit... :)
Re: Iridium browser install issue
Posted: Sun Aug 18, 2019 7:37 am
by PondLife
You can stop the keyring nonsense by editing the launcher command to read “%U --password-store=basic” at the end (no quote marks).
Re: Iridium browser install issue
Posted: Sun Aug 18, 2019 7:48 am
by Huckleberry Finn
PondLife wrote: Sun Aug 18, 2019 7:37 am
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 :)
Re: Iridium browser install issue
Posted: Tue Sep 03, 2019 7:22 pm
by 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.
Re: Iridium browser install issue
Posted: Tue Sep 03, 2019 8:29 pm
by 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.
Re: Iridium browser install issue
Posted: Thu Dec 12, 2019 10:55 am
by ASL
MX 19_x64 here. Same problem, same solution as above. Talk about mystery line :)
Re: Iridium browser install issue
Posted: Thu Dec 12, 2019 11:44 am
by fehlix
ASL wrote: Thu Dec 12, 2019 10:55 am
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"?
Re: Iridium browser install issue
Posted: Thu Dec 12, 2019 12:33 pm
by 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.