After the upgrade to polkit I plug in a usb stick and get this error:

So I try to eject and get this error:

A quick peek at the Changelog notes should prove most illuminating:
Usually what I do is manually remove old versions of mozjs before installing the new one. That way, there's no confusion as to what version of libraries polkit is utilizing. Hope this helps!

Happy Slacking!

Yes. I followed directions and removed the old one before installing the new one.

Oh - the shutdown menu is modified now and can't shutdown, only logout or switch user. When I get back from the dump later I will downgrade some packages and see what happens

I had similar problems (see https://www.linuxquestions.org/quest...rd-4175682218/).
I had to revert polkit, glib2 and mozjs to get rid of the problems.

I guess if you are running my KDE Plasma5 packages with elogind and the rebuilt polkit package (to support elogind) this polkit upgrade will break your Plasma5 installation.
Now would be a good time for Plasma5 to replace KDE4 in Slackware-current since I stopped providing updates to my 'ktown' package set for Plasma5.

3 members found this post helpful.

The package for "polkit-0.117 (alien)" will be missing the "mozjs68" libraries if you upgrade to the newer "mozjs78" package and remove the old package. polkit-0.117 can't be rebuilt against mozjs78 and has to be upgraded to polkit-0.118.

I'm testing out a rebuilt polkit-0.118 "alien" package with Eric's slackbuild. I grabbed the source from here: https://gitlab.freedesktop.org/polki...t/-/tree/0.118 and rsync'd Eric's slackbuild from here: http://bear.alienbase.nl/mirrors/ali...t/deps/polkit/ His script auto detects the version so you just have to move the 0.117 tarball out and move the 0.118 tar in its place. Built fine for me against mozjs78 so I'm testing out an upgraded package for polkit-0.118. (Eric if you read this, any downsides to this?)

I suspect there will be more threads like this as current continues moving forward without plasma 5. I hope that plasma 5 can be included in slackware offically sometime soon. Maybe we should keep a dedicated thread (here or Eric's blog) to keep track of the breakage for those of us who like the plasma 5 desktop and want to keep using it.

4 members found this post helpful.

Probably just installing the old mozjs68 alongside the new mozjs78 will fix the Plasma5 issue. Get a copy of the old mozjs68 package at http://slackware.uk/cumulative/slack...r-x86_64-2.txz

6 members found this post helpful.

I just reverted all the upgrades from yesterday. Things work again and I will run like that for the foreseeable future

EDIT - I suppose we know what caused this to happen and what needs to happen to fix it so I am marking this thread solved

I run Plasma5 in slackware64-current, and installed mozjs78 (after removing mozjs68), together with polkit-0.118

I don't see any change, everything seems to work well

1 members found this post helpful.

Well, I woke early today and with a clearer head was able to get er done. Alien Bob, you were right. I was able to install and run both mozjs68 and mozjs78 at the same time.
You earned yourself a helpful rating from me with that post. That was my starting point and since both of mozjs can run side by each ...

Anyway, file by file I updated and then rebooted my laptop (because after reverting everything yesterday it took a reboot to restore behavior to normal). File by file, upgrade and reboot then check to see if there were any unpleasant changes.

I also did this (was in the changelog):

It took a long time but there were only two surprises. First surprise was that updating polkit didn't mess anything up. Second surprise was that after all this the last thing I did was remove mozjs68 and now everything works and all updates are done.

Thank you because it was your comment that convinced me to try again and you are correct in that everything seems to work well
You earned yourself a helpful rating from me with your post.

Thanks Alien Bob and Toutatis

Yes, re-installing mozjs68 alongside the new mozjs78 fixed the borked shutdown options for me.

1 members found this post helpful.

I took the same route as 0XBF. Built polkit-118 source using Alien Bob's build with elogind support. So far all is well.

2 members found this post helpful.

I haven't had any issues yet either with the rebuilt polkit-118 package. I did have the afterthought that it would probably be easier to just get the polkit-118 source from a slackware-current mirror and build it with Eric's slackbuild, instead of taking the source from freedesktop's git page. I should have thought of it earlier since I have a local mirror with the source already sitting right there.

Also might be a good idea to put a custom tag any rebuilt packages so it's easy to revert if/when Plasma5 makes its way into current.

Agree. That's what I do. I added a directory to my build tree for this situation, after the package is built (and tagged) I place it in my local repository. This ensures I can use slackpkg w/slackpkg+ to update my other installs off my LAN.

This was a one package issue so not that hard to handle. Hopefully Plasma 5 with get added before it get to be more than single package fixes. That said, I am prepared to build ktown on my own if it gets to that point.

Using the scripts, patches, etc from:
http://bear.alienbase.nl/mirrors/ali...t/deps/polkit/
and the source from:
https://gitlab.freedesktop.org/polki...t/-/tree/0.118
or the build from:
https://mirror.slackbuilds.org/slack...urce/l/polkit/
failed with gtk-doc errors.

*** Begin Screen Dump ***
...
Making all in polkit
make[3]: Entering directory '/tmp/polkit-0.118/docs/polkit'
DOC Scanning header files
Traceback (most recent call last):
File "/usr/share/gtk-doc/python/gtkdoc/config.py", line 5, in <module>
from gtkdoc_uninstalled import builddir
ModuleNotFoundError: No module named 'gtkdoc_uninstalled'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/bin/gtkdoc-scan", line 33, in <module>
from gtkdoc import common, config, scan
File "/usr/share/gtk-doc/python/gtkdoc/common.py", line 29, in <module>
from . import config
File "/usr/share/gtk-doc/python/gtkdoc/config.py", line 8, in <module>
from gtkdoc.config_data import *
ModuleNotFoundError: No module named 'gtkdoc.config_data'
make[3]: *** [Makefile:773: scan-build.stamp] Error 1
make[3]: Leaving directory '/tmp/polkit-0.118/docs/polkit'
make[2]: *** [Makefile:446: all-recursive] Error 1
make[2]: Leaving directory '/tmp/polkit-0.118/docs'
make[1]: *** [Makefile:501: all-recursive] Error 1
make[1]: Leaving directory '/tmp/polkit-0.118'
make: *** [Makefile:433: all] Error 2
*** End Screen Dump ***