LinuxQuestions.org - [SOLVED] SlackBuilds Chromium install fails

Page 1 of 2

Show 50 post(s) from this thread on one page

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - SlackBuilds Chromium install fails (https://www.linuxquestions.org/questions/slackware-14/slackbuilds-chromium-install-fails-4175615589/)

thethinker

10-13-2017 09:06 AM

SlackBuilds Chromium install fails

Hey All,
Installing Chromium on Slackware 14.2 64 bit using the Slackbuilds package, and getting the following errors:

Code:

chromium-53.0.2785.143/chromeos/third_party/android_bionic_libc/kernel/uapi/

chromium-53.0.2785.143/chromeos/third_party/android_bionic_libc/kernel/uapi/linux/

chromium-53.0.2785.143/chromeos/third_party/android_bionic_libc/kernel/uapi/linux/binder.h

chromium-53.0.2785.143/chromeos/third_party/android_bionic_libc/README.chromium

chmod: cannot operate on dangling symlink './third_party/skia/tools/gyp'

chmod: cannot operate on dangling symlink './third_party/libxslt/config.guess'

chmod: cannot operate on dangling symlink './third_party/libxslt/COPYING'

chmod: cannot operate on dangling symlink './third_party/libxslt/compile'

chmod: cannot operate on dangling symlink './third_party/libxslt/install-sh'

chmod: cannot operate on dangling symlink './third_party/libxslt/depcomp'

chmod: cannot operate on dangling symlink './third_party/libxslt/missing'

chmod: cannot operate on dangling symlink './third_party/libxslt/config.sub'

chmod: cannot operate on dangling symlink './third_party/mesa/src/src/gallium/state_trackers/d3d1x/w32api'

chmod: cannot operate on dangling symlink './third_party/webrtc/tools/e2e_quality/audio/perf'

chmod: cannot operate on dangling symlink './third_party/webrtc/examples/objc/.clang-format'

patching file third_party/WebKit/Source/wtf/allocator/PageAllocator.cpp

Updating projects from gyp files...

./chromium.SlackBuild: line 165: ninja: command not found

Anyone have any thoughts? I found another reference for this error:

https://www.linuxquestions.org/questions/slackware-14/update-chromium-slackbuild-4175457561/

The suggestion there is "there was a gcc upgrade" which broke this - if we think that's the case, is there any advice out there to fix this?

bassmadrigal

10-13-2017 09:31 AM

You really shouldn't run the chromium version on SBo (at least not the version that's up there now). It's quite outdated. v53 was released back in Aug 2016. There's been a lot of security fixes since then. (I'm not even sure we should keep chromium on SBo if it isn't kept relatively recent.)

Instead, I'd recommend using Alien Bob's chromium package. If you really want to compile it, you can use his SlackBuild, located a few directories up.

If you really want to build the one on SBo, you at least need to have ninja installed (which is listed as a required dependency). According to the following line, you don't have it installed (or it's installed improperly):

Code:

./chromium.SlackBuild: line 165: ninja: command not found

thethinker

10-13-2017 08:44 PM

Quote:

Originally Posted by bassmadrigal (Post 5769499)

Instead, I'd recommend using Alien Bob's chromium package. If you really want to compile it, you can use his SlackBuild, located a few directories up.

Nope.

Code:

$ chromium-browser &

$ [6652:6682:1013/214145.240941:FATAL:nss_util.cc(632)] NSS_VersionCheck("3.26") failed. NSS >= 3.26 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.

#0 0x55a52acef445 <unknown>

#1 0x55a52ad081dd <unknown>

#2 0x55a52b6f9b40 <unknown>

#3 0x55a52b6f9f68 <unknown>

#4 0x55a52b6f9fd7 <unknown>

#5 0x55a52b6194d5 <unknown>

#6 0x55a52b5b87f5 <unknown>

#7 0x55a52b4f15c7 <unknown>

#8 0x55a52aaef851 <unknown>

#9 0x55a52aaefb18 <unknown>

#10 0x55a52aae17e2 <unknown>

#11 0x55a529824107 <unknown>

#12 0x55a52982344f <unknown>

#13 0x55a52ad5906d <unknown>

#14 0x55a52ad5392d <unknown>

#15 0x7f46aa57b684 start_thread

#16 0x7f46aa2b1efd __clone



Received signal 6

#0 0x55a52acef445 <unknown>

#1 0x55a52916718f <unknown>

#2 0x55a52acef7dd <unknown>

#3 0x7f46aa5853b0 <unknown>

#4 0x7f46aa1e03f8 __GI_raise

#5 0x7f46aa1e1ffa __GI_abort

#6 0x55a52acef265 <unknown>

#7 0x55a52ad08255 <unknown>

#8 0x55a52b6f9b40 <unknown>

#9 0x55a52b6f9f68 <unknown>

#10 0x55a52b6f9fd7 <unknown>

#11 0x55a52b6194d5 <unknown>

#12 0x55a52b5b87f5 <unknown>

#13 0x55a52b4f15c7 <unknown>

#14 0x55a52aaef851 <unknown>

#15 0x55a52aaefb18 <unknown>

#16 0x55a52aae17e2 <unknown>

#17 0x55a529824107 <unknown>

#18 0x55a52982344f <unknown>

#19 0x55a52ad5906d <unknown>

#20 0x55a52ad5392d <unknown>

#21 0x7f46aa57b684 start_thread

#22 0x7f46aa2b1efd __clone

  r8: ffffffffcd8139f0  r9: ffffffffcd8139e0 r10: 0000000000000008 r11: 0000000000000206

 r12: 00007f465e7fb240 r13: 00007f465e7fb740 r14: 00007f465e7fb730 r15: 00007f465e7fb260

  di: 00000000000019fc  si: 0000000000001a1a  bp: 00007f465e7fb040  bx: 00007f465e7fb738

  dx: 0000000000000006  ax: 0000000000000000  cx: 00007f46aa1e03f8  sp: 00007f465e7faea8

  ip: 00007f46aa1e03f8 efl: 0000000000000206 cgf: 0000000000000033 erf: 0000000000000000

 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000

[end of stack trace]

Calling _exit(1). Core file will not be generated.

Working on updating NSS now, but does not appear obvious.

ponce

10-14-2017 12:32 AM

most probably your system is not updated with the latest patches, because mozilla-nss has been updated on slackware 14.2 more than one month ago: from its changelog

Code:

Fri Sep  8 17:56:01 UTC 2017

[...]

patches/packages/mozilla-nss-3.31.1-x86_64-1_slack14.2.txz:  Upgraded.

  Upgraded to nss-3.31.1 and nspr-4.16.

  This is a bugfix release.

thethinker

10-14-2017 08:45 AM

Quote:

Originally Posted by ponce (Post 5769737)

most probably your system is not updated with the latest patches, because mozilla-nss has been updated on slackware 14.2 more than one month ago: from its changelog

Code:

Fri Sep  8 17:56:01 UTC 2017

[...]

patches/packages/mozilla-nss-3.31.1-x86_64-1_slack14.2.txz:  Upgraded.

  Upgraded to nss-3.31.1 and nspr-4.16.

  This is a bugfix release.

So because the 14.2 install disk I used is more than one month old? I guess I didn't think Slackware updates happened that way...

EDIT: I take that back, I downloaded this .iso on 10/8/17. I'll see about updating Mozilla.

Alien Bob

10-14-2017 10:57 AM

Quote:

Originally Posted by thethinker (Post 5769838)

The Slackware 14.2 ISO does not get modified over time. When you install Slackware from a release-ISO you get what was available at the time of release. Since that Slackware 14.2 release, 16 months have passed and a lot of (security) patches were published online.
When you install Slackware it does not automatically update you to the latest patches. You need to do that yourself.
And until you install these patches, you run the risk of installing binary packages that were compiled against the latest Slackware 14.2 which results in runtime errors.

Slackpkg will help you install the missing patches: https://docs.slackware.com/slackware:beginners_guide?s[]=patches#watching_for_updated_packages

thethinker

10-14-2017 11:23 AM

Quote:

Originally Posted by Alien Bob (Post 5769897)

Does not appear that's the problem:

Code:

# slackpkg update



Updating the package lists...

        Downloading...

                        Downloading http://mirrors.slackware.com/slackware/slackware64-14.2/ChangeLog.txt...

URL transformed to HTTPS due to an HSTS policy

--2017-10-14 16:20:55--  https://mirrors.slackware.com/slackware/slackware64-14.2/ChangeLog.txt

Resolving mirrors.slackware.com (mirrors.slackware.com)... 207.223.116.213

Connecting to mirrors.slackware.com (mirrors.slackware.com)|207.223.116.213|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: 437933 (428K) [text/plain]

Saving to: '/tmp/slackpkg.diQZH8/ChangeLog.txt'



/tmp/slackpkg.diQZH 100%[===================>] 427.67K  132KB/s    in 3.2s    



2017-10-14 16:20:59 (132 KB/s) - '/tmp/slackpkg.diQZH8/ChangeLog.txt' saved [437933/437933]





                No changes in ChangeLog.txt between your last update and now.

                Do you really want to download all other files (y/N)?

(I mean, I did the slackpkg update when I installed a few days ago, but this is from just now)

ponce

10-14-2017 11:37 AM

check which mozilla-nss libraries you have installed in your system

Code:

$ ls -la /var/log/packages/mozilla-nss-* 

-rw-r--r-- 1 root root 5943 Sep 18 12:16 /var/log/packages/mozilla-nss-3.31.1-x86_64-1_slack14.2

$ nss-config --version

3.31.1

$ nspr-config --version

4.16.0

$ ls -la /usr/lib64/libnspr4.so /usr/lib64/libnss3.so 

-rwxr-xr-x 1 root root  244560 Sep  8 19:29 /usr/lib64/libnspr4.so*

-rwxr-xr-x 1 root root 1193552 Sep  8 19:29 /usr/lib64/libnss3.so*

thethinker

10-14-2017 01:40 PM

Quote:

Originally Posted by ponce (Post 5769917)

check which mozilla-nss libraries you have installed in your system

Code:

$ ls -la /var/log/packages/mozilla-nss-* 

-rw-r--r-- 1 root root 5943 Sep 18 12:16 /var/log/packages/mozilla-nss-3.31.1-x86_64-1_slack14.2

$ nss-config --version

3.31.1

$ nspr-config --version

4.16.0

$ ls -la /usr/lib64/libnspr4.so /usr/lib64/libnss3.so 

-rwxr-xr-x 1 root root  244560 Sep  8 19:29 /usr/lib64/libnspr4.so*

-rwxr-xr-x 1 root root 1193552 Sep  8 19:29 /usr/lib64/libnss3.so*

Yeah, it shows they are not updated:

Code:

$ ls -la /var/log/packages/mozilla-nss-*

-rw-r--r-- 1 root root 5772 Oct  7 23:49 /var/log/packages/mozilla-nss-3.23-x86_64-1

$ nss-config --version

shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

3.23.

$nspr-config --version

shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

4.12.0

$ ls -la /usr/lib64/libnspr4.so /usr/lib64/libnss3.so 

-rwxr-xr-x 1 root root  244592 Mar  9  2016 /usr/lib64/libnspr4.so

-rwxr-xr-x 1 root root 1181136 Mar  9  2016 /usr/lib64/libnss3.so

I tried to install an updated nss, which seemed to work but the chromium build from alien is obviously finding these. So upgrading mozilla by hand seems to be the answer. Any advice?

(And any thoughts about that random shell-init error?)

ponce

10-14-2017 02:01 PM

if I were you I would:
- avoid updating anthing by hand and use only official packages: now you may have some libraries in your system that, at some point, may conflict with others installed by the official packages;
- ask myself why the mozilla-nss package has not been updated by slackpkg: do you have something in your /etc/slackpkg/blacklist that held it at a previous version?
you can also solve this by running upgradepkg by hand, but either you do always upgrades manually or you should definitely fix the way slackpkg upgrades your installed packages.

Alien Bob

10-14-2017 02:10 PM

The "shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory" message could be caused because your working directory was deleted in another shell process.

Alien Bob

10-14-2017 02:16 PM

And not all mirrors behind mirrors.slackware.com seem to be fully up to date. I only tried the first one on the list, https://mirrors.netix.net/slackware/...-14.2/patches/ and that is missing about everything.
Who knows what the status is of the others. The mirror you used may be incomplete as well.

montagdude

10-14-2017 03:02 PM

Quote:

Originally Posted by thethinker (Post 5769909)

Does not appear that's the problem:

Code:

# slackpkg update



Updating the package lists...

        Downloading...

                        Downloading http://mirrors.slackware.com/slackware/slackware64-14.2/ChangeLog.txt...

URL transformed to HTTPS due to an HSTS policy

--2017-10-14 16:20:55--  https://mirrors.slackware.com/slackware/slackware64-14.2/ChangeLog.txt

Resolving mirrors.slackware.com (mirrors.slackware.com)... 207.223.116.213

Connecting to mirrors.slackware.com (mirrors.slackware.com)|207.223.116.213|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: 437933 (428K) [text/plain]

Saving to: '/tmp/slackpkg.diQZH8/ChangeLog.txt'



/tmp/slackpkg.diQZH 100%[===================>] 427.67K  132KB/s    in 3.2s    



2017-10-14 16:20:59 (132 KB/s) - '/tmp/slackpkg.diQZH8/ChangeLog.txt' saved [437933/437933]





                No changes in ChangeLog.txt between your last update and now.

                Do you really want to download all other files (y/N)?

(I mean, I did the slackpkg update when I installed a few days ago, but this is from just now)

You did `slackpkg update`, but did you do `slackpkg upgrade-all`? The former only downloads the latest ChangeLogs; the latter actually upgrades packages that are out of date.

thethinker

10-14-2017 09:25 PM

Quote:

Originally Posted by montagdude (Post 5770002)

You did `slackpkg update`, but did you do `slackpkg upgrade-all`? The former only downloads the latest ChangeLogs; the latter actually upgrades packages that are out of date.

Wow that is very clearly the problem. I've never really used slackpkg before, so I was following the "Slackware Beginner's Guide" on docs.slackware, which literally stop at "slackpkg update". Clearly I should have looked more closely at how the manager works, but if it's a "beginner's guide", it should be clear that after you run that command, your system is *not* updated.

Anyway, I'm updated now and pretty confident that will be the fix. Thanks!

montagdude

10-14-2017 11:26 PM

Quote:

Originally Posted by thethinker (Post 5770083)

Yeah, I agree that page is misleading. This one is more complete:

https://docs.slackware.com/slackware:slackpkg

If you are familiar with Ubuntu, the difference between `slackpkg update` and `slackpkg upgrade-all` is basically the same as the difference between `apt-get update` and `apt-get upgrade`.

All times are GMT -5. The time now is 12:31 AM.

Page 1 of 2

Show 50 post(s) from this thread on one page