[SOLVED] XFCE shutdown menu grayed out after current update

colorpurple21859 · 03-26-2016, 02:03 PM

Downgrading polkit fixed all the issues I was having. Thanks for the suggestion

USUARIONUEVO · 03-26-2016, 03:58 PM

Probably all polkit family packages need fixes , or return down the polkit package.

Here , a big lag to start machine...and filebrowser FAST AS A TRUTLE. waiting fix.

brobr · 03-26-2016, 05:25 PM

The thread-title issue also comes along in the other thread which supplies a working solution. No need to downgrade polkit.

USUARIONUEVO · 03-26-2016, 05:50 PM

Quote:

Originally Posted by brobr

The thread-title issue also comes along in this thread which supplies a working solution. No need to downgrade polkit.

After do that , my system go slow...no message arroun user polkitd, but my machine converts in to a turttle.

1 minute to start desktop.

I found another nice ...gparted no start

/usr/sbin/gparted_polkit %f

Quote:

Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error

rg.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PolicyKit1': timed out

need to run ,with another one

Quote:

/usr/sbin/gparted

brobr · 03-26-2016, 06:02 PM

Yes, same here. My comp hung on trying to log out of xfce (or shutdown). I followed the steps advised (see post post5521691) and all is back to normal. Note that I had to shut down the comp and normal behavior was only restored after the next boot-up.

hitest · 03-26-2016, 06:24 PM

I implemented the two additions that rworkman suggested in this thread and my shutdown menu is restored again.
As Robby suggested I'll wait and see what Pat does. Thanks for your help folks.

colorpurple21859 · 03-26-2016, 08:06 PM

I also upgraded back to the current polkit and did the suggestions mentioned in the other thread and everything seems to be working again.

Philip Lacroix · 03-26-2016, 08:45 PM

There's a new update available for -current (Sat Mar 26 23:20:34 UTC 2016) which includes a rebuild of polkit, fixing the mentioned issues. Everything is working fine again.

Thanks to PV and Team!

hitest · 03-26-2016, 08:48 PM

Quote:

Originally Posted by Philip Lacroix

There's a new update available for -current (Sat Mar 26 23:20:34 UTC 2016) which includes a rebuild of polkit, fixing the mentioned issues. Everything seems to be working fine again.

Thanks to PV and Team!

Many thanks, Pat. Marking this as solved.

USUARIONUEVO · 03-26-2016, 10:43 PM

After last update all return to normal works.

Thanks.

burdi01 · 03-28-2016, 07:22 AM

Yes, the Sun Mar 27 19:39:10 UTC 2016 update resolved the problem for me too. BUT upgrading the polkit-compat32 package re-introduced the problem!
I re-resolved the problem by a "slackpkg reinstall polkit" command.

bassmadrigal · 03-28-2016, 07:52 AM

You'll probably want to wait until Eric has a chance to update his multilib (or grab the 32bit packages and convert them yourself).

You can monitor his work using his ChangeLog.

Alien Bob · 03-28-2016, 07:54 AM

Quote:

Originally Posted by burdi01

Yes, the Sun Mar 27 19:39:10 UTC 2016 update resolved the problem for me too. BUT upgrading the polkit-compat32 package re-introduced the problem!
I re-resolved the problem by a "slackpkg reinstall polkit" command.

I do not have a "polkit-compat32" package as part of my multilib package set. Why did you create one? Do you have a binary-only program that needs it or have you been compiling 32bit packages on your multilib computer and had to add it as a dependency?

burdi01 · 03-28-2016, 10:35 AM

@Eric: I use multilib to build 32-bit packages for Parted Magic.
And yes, I added polkit-compat32 as a dependency.
In my enthousiasm I forgot that polkit is one of my 26 non-standard compat32 packages ...
This is the first time that such a compat32 package causes a problem like this. To be honest I have not looked into the details as a reinstall of the 64-bit package resolves the problem.
If you are interested I can dig deeper and report back.
Regards, Dick

burdi01 · 03-31-2016, 06:50 AM

It took me some time, but I found the problem: the polkit 64-bit package creates its polkit-1/ directory in /usr/lib instead of /usr/lib64 and the 32-bit package happily replaces the binaries therein with its 32-bit versions.