google-chrome-current in Porteus 4.0 Xfce

Non release banter
Post Reply
Kulle
Shogun
Shogun
Posts: 310
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

google-chrome-current in Porteus 4.0 Xfce

Post#1 by Kulle » 03 Feb 2021, 11:30

libxkbcommon is missing in Porteus 4.0 Xfce.
Is required for google-chrome-current:

Code: Select all

guest@porteus:~/Downloads$ activate google-chrome-stable_current_amd64.xzm 
glibtop(c=7641): [DEBUG] open.c:53 glibtop_open_l(): SIZEOF: 40 - 65648 - 248 - 65624 - 224 - 65624
glibtop(c=7641): [DEBUG] open.c:163 glibtop_open_l(): Calling sysdeps open function.
glibtop(c=7641): [DEBUG] init.c:229 glibtop_init_s(): init_s with features=0x7ffffff and flags=0
Quiet mode: off
Updating shared library links:  /sbin/ldconfig
Updating XFCE menu: update-desktop-database
guest@porteus:~/Downloads$ google-chrome-stable 
/usr/bin/google-chrome-stable: error while loading shared libraries: libxkbcommon.so.0: cannot open shared object file: No such file or directory
guest@porteus:~/Downloads$ activate libxkbcommon-1.0.3-alt1.x86_64.xzm 
glibtop(c=7766): [DEBUG] open.c:53 glibtop_open_l(): SIZEOF: 40 - 65648 - 248 - 65624 - 224 - 65624
glibtop(c=7766): [DEBUG] open.c:163 glibtop_open_l(): Calling sysdeps open function.
glibtop(c=7766): [DEBUG] init.c:229 glibtop_init_s(): init_s with features=0x7ffffff and flags=0
Quiet mode: off
Updating shared library links:  /sbin/ldconfig
guest@porteus:~/Downloads$ google-chrome-stable 
[7831:7831:0203/122056.187020:ERROR:browser_dm_token_storage_linux.cc(94)] Error: /etc/machine-id contains 0 characters (32 were expected).

The Error: /etc/machine-id contains 0 characters (32 were expected).
can be ignored

Kulle
Shogun
Shogun
Posts: 310
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

google-chrome-current in Porteus 4.0 Xfce

Post#2 by Kulle » 03 Feb 2021, 13:26

The current slimjet browser also requires libxkbcommon.

Kulle
Shogun
Shogun
Posts: 310
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

google-chrome-current in Porteus 4.0 Xfce

Post#3 by Kulle » 03 Feb 2021, 13:37

But the current Chromium browser (88.0.4324.96) doesn't need libxkbcommon !?

User avatar
skladby
Ronin
Ronin
Posts: 3
Joined: 29 Dec 2020, 16:56
Distribution: 5

google-chrome-current in Porteus 4.0 Xfce

Post#4 by skladby » 25 Feb 2021, 07:51

Same for "official" google-chrome-88.0.4324.150-x86_64-en-US-1.xzm on http://dl.porteus.org/x86_64/Porteus-v5.0/modules/ and for "self-XZMed" Opera 74, Vivaldi 3.6, and Edge Dev 90 - so obviously for anything based on Chromium. BUT if you download Chromium itself "right off the trunk" from https://download-chromium.appspot.com/, you may get a fat developer version with a bunch of libs "on-board", as opposed to user versions where applications expect libs to be provided by the system.

User avatar
skladby
Ronin
Ronin
Posts: 3
Joined: 29 Dec 2020, 16:56
Distribution: 5

google-chrome-current in Porteus 4.0 Xfce

Post#5 by skladby » 25 Feb 2021, 08:19

OK, this is a problem of the Xfce flavor - at least Chrome 88 (from dl.porteus.org as well as self XZMed) starts well if addtionally 003-openbox.xzm is activated which contains a bunch of libxkbcommon SOs.

Post Reply