Iridium browser install issue

[ChrisBE]

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?

[fehlix]

... 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!

[fehlix]

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.

[ChrisBE]

... 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!

[ChrisBE]

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.

[fehlix]

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"

[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.

[fehlix]

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?

[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.

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.

[fehlix]

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