LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-16-2020, 12:34 PM   #1
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 659

Rep: Reputation: 265Reputation: 265Reputation: 265
Tue Sep 15 18:51:00 UTC 2020 - polkit upgrade


After the upgrade to polkit I plug in a usb stick and get this error:
Code:
You are not authorized to mount this device

So I try to eject and get this error:
Code:
Failed to eject
Not authorized to perform operation (polkit authority not available and caller is not uid 0)
 
Old 09-16-2020, 12:40 PM   #2
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 806
Blog Entries: 9

Rep: Reputation: 544Reputation: 544Reputation: 544Reputation: 544Reputation: 544Reputation: 544
Quote:
Originally Posted by Gordie View Post
After the upgrade to polkit I plug in a usb stick and get this error:
Code:
You are not authorized to mount this device

So I try to eject and get this error:
Code:
Failed to eject
Not authorized to perform operation (polkit authority not available and caller is not uid 0)
A quick peek at the Changelog notes should prove most illuminating:
Quote:
Tue Sep 15 18:51:00 UTC 2020
a/libgudev-234-x86_64-1.txz: Upgraded.
ap/htop-3.0.2-x86_64-1.txz: Upgraded.
l/glib2-2.66.0-x86_64-2.txz: Rebuilt.
Build against system gtk-doc and don't bundle a newer version. You'll need
to reinstall the linuxdoc-tools package to restore the correct version of
gtk-doc. Thanks to chrisVV.
l/mozjs68-68.11.0esr-x86_64-2.txz: Removed.
l/mozjs78-78.2.0esr-x86_64-1.txz: Added.
This is needed by the new version of polkit.
l/polkit-0.118-x86_64-1.txz: Upgraded.
This requires the new mozjs78 package.

x/libva-2.9.0-x86_64-1.txz: Upgraded.
x/libva-utils-2.9.0-x86_64-1.txz: Upgraded
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!
 
Old 09-16-2020, 01:19 PM   #3
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 659

Original Poster
Rep: Reputation: 265Reputation: 265Reputation: 265
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
 
Old 09-16-2020, 01:31 PM   #4
z80
Member
 
Registered: Jul 2019
Location: Europe
Distribution: Slackware
Posts: 41

Rep: Reputation: 18
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.
 
Old 09-16-2020, 01:49 PM   #5
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,137

Rep: Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999
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.
Old 09-16-2020, 02:12 PM   #6
0XBF
Member
 
Registered: Nov 2018
Location: Winnipeg
Distribution: Slackware, Artix
Posts: 228

Rep: Reputation: 185Reputation: 185
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.

Last edited by 0XBF; 09-16-2020 at 02:19 PM.
 
4 members found this post helpful.
Old 09-16-2020, 03:23 PM   #7
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,137

Rep: Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999Reputation: 6999
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.
Old 09-16-2020, 04:56 PM   #8
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 659

Original Poster
Rep: Reputation: 265Reputation: 265Reputation: 265
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

Last edited by Gordie; 09-16-2020 at 08:15 PM.
 
Old 09-17-2020, 01:07 AM   #9
Toutatis
Member
 
Registered: Feb 2013
Posts: 271

Rep: Reputation: Disabled
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.
Old 09-17-2020, 10:27 AM   #10
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware Linux
Posts: 659

Original Poster
Rep: Reputation: 265Reputation: 265Reputation: 265
Quote:
Originally Posted by Alien Bob View Post
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
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):

Code:
You'll need to reinstall the linuxdoc-tools package to restore the correct version of 
gtk-doc
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.

Quote:
Originally Posted by Toutatis View Post
I run Plasma5 in slackware64-current, and installed mozjs78 (after removing mozjs68), together with polkit-0.118

I do't see any change, everything seems to work well
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
 
Old 09-18-2020, 01:18 AM   #11
drgibbon
Member
 
Registered: Nov 2014
Distribution: Slackware64 -current
Posts: 773

Rep: Reputation: 519Reputation: 519Reputation: 519Reputation: 519Reputation: 519Reputation: 519
Quote:
Originally Posted by Alien Bob View Post
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
Yes, re-installing mozjs68 alongside the new mozjs78 fixed the borked shutdown options for me.
 
1 members found this post helpful.
Old 09-18-2020, 07:46 AM   #12
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,296

Rep: Reputation: 555Reputation: 555Reputation: 555Reputation: 555Reputation: 555Reputation: 555
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.
Old 09-18-2020, 05:02 PM   #13
0XBF
Member
 
Registered: Nov 2018
Location: Winnipeg
Distribution: Slackware, Artix
Posts: 228

Rep: Reputation: 185Reputation: 185
Quote:
Originally Posted by chrisretusn View Post
I took the same route as 0XBF. Built polkit-118 source using Alien Bob's build with elogind support. So far all is well.
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.
 
Old 09-19-2020, 02:49 AM   #14
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,296

Rep: Reputation: 555Reputation: 555Reputation: 555Reputation: 555Reputation: 555Reputation: 555
Quote:
Originally Posted by 0XBF View Post
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.
 
Old 09-19-2020, 11:44 AM   #15
linux91
Member
 
Registered: Feb 2004
Location: Williamson, New York, USA
Distribution: (Minix), SLS, Slackware 1.0-14.2, Current
Posts: 33

Rep: Reputation: 6
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 ***

Last edited by linux91; 09-19-2020 at 12:53 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Current64: Fri Sep 21 18:51:07 UTC updates: glibc 2.27 -> 2.28: libicdn burdi01 Slackware 1 09-23-2018 06:09 AM
"Tue Jul 15 23:53:10 UTC 2014" X updates breaks X grissiom Slackware 29 07-21-2014 09:12 PM
LXer: Those Polkit/PolicyKit XML files a pain to view? Polkit Explorer now avaiable... LXer Syndicated Linux News 0 03-31-2013 03:42 PM
awk command line: blank line record sep, new line field sep robertmarkbram Programming 4 02-21-2010 05:25 AM
LXer: KDE extends Polkit support to polkit-1 LXer Syndicated Linux News 0 12-26-2009 12:00 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:32 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration