[SOLVED] ldd /usr/lib/polkit-1/polkitd returns libmozjs-102.so.0 => not found

RandomTroll · 03-22-2024, 08:03 AM

Code:

/usr/lib/polkit-1/polkitd

returns

Quote:

libmozjs-102.so.0 => not found

latest polkit package, polkit-123-x86_64-1.txz I never use polkitd, so I don't care

Thom1b · 03-22-2024, 08:22 AM

Hi,
Do you install mozjs102 package?

hazel · 03-22-2024, 08:22 AM

That's javascript. Polkit uses it for some of its configuration files. But you should have it as part of firefox.

RandomTroll · 03-22-2024, 09:23 AM

Whoops! It's my fault. Because upgrade of mozjs packages don't remove old ones, I do it myself. I didn't notice that Slackware has 2 mozjs packages. Sorry. I still think this is a defect of mozjs.

Thom1b · 03-22-2024, 10:52 AM

Usually when there is a new mozjs$NEWVERSION package, mozjs$OLDVERSION is removed. That's not the case for mozjs102.

reddog83 · 03-22-2024, 02:33 PM

Mozjs115 was built with the library name libmozjs102 i suggest to reinstall mozjs102 and that will fix it cause the correct name for mozjs115 library is libmozjs115

volkerdi · 03-22-2024, 03:00 PM

Quote:

Originally Posted by reddog83

Mozjs115 was built with the library name libmozjs102 i suggest to reinstall mozjs102 and that will fix it cause the correct name for mozjs115 library is libmozjs115

I don't believe that glitch ever caused a broken symlink. It just caused the first build of mozjs115 to include the same symlinks that were in mozjs102.

But yes, now we are seeing why we didn't just call this one "mozjs".

RandomTroll · 03-23-2024, 03:26 AM

Quote:

Originally Posted by Thom1b

Usually when there is a new mozjs$NEWVERSION package, mozjs$OLDVERSION is removed.

That has often not-happened with me, as I have reported in LQ before.

polkit was the only executable or library that objected to the lack of mozjs102. Could it have been built against mozjs115?

0XBF · 03-23-2024, 01:25 PM

Quote:

Originally Posted by RandomTroll

polkit was the only executable or library that objected to the lack of mozjs102. Could it have been built against mozjs115?

polkit-124 is the newer version that uses mozjs115. Slackware-current is still using polkit-123 at the moment, which uses the mozjs102 version.

I tried building polkit-124 and it fails on slackware-current due to some flawed logic in the meson.build file where it tries to set the 'sysusers.d' directory but fails on non-systemd installs. The Artix linux guys have a patch that fixes that issue by making that a build option instead: https://gitea.artixlinux.org/package...susers-d.patch

The build succeeds with the patch.

I haven't runtime tested it since I don't have a machine running -current that's up-to-date at the moment, but as it stands, that version doesn't build as-is from upstream and needs some fixing.

RandomTroll · 03-23-2024, 11:10 PM

Quote:

Originally Posted by 0XBF

polkit-124 is the newer version that uses mozjs115. Slackware-current is still using polkit-123 at the moment, which uses the mozjs102 version.

I tried building polkit-124...

Thanks. The substance of my question was whether polkit is outdated or are there features of mozjs102 that mozjs115 lacks. It seems the former.

0XBF · 03-24-2024, 10:05 AM

In the meanwhile, polkit-123 was switched to build with duktape and mozjs102 has been dropped, making this all moot:

Code:

l/duktape-2.7.0-x86_64-1.txz:  Added.
  Needed by polkit.
l/polkit-123-x86_64-2.txz:  Rebuilt.
  Use duktape instead of mozjs102 as the JavaScript engine.
l/mozjs102-102.15.1esr-x86_64-2.txz:  Removed.

RandomTroll · 03-24-2024, 11:36 AM

Quote:

Originally Posted by 0XBF

polkit-123 was switched to build with duktape and mozjs102 has been dropped..

Beat me to it, curse you! I just downloaded the Slack source and built it, found what you reported. Thanks.