Page 1 of 1

No Access to MCC or shutdown

PostPosted: May 26th, '16, 17:51
by Garthhh
Mageia 5 64bit
KDE\
shutdown button clicks, nothing happens
MCC menu icon clicks menu hide, no result

Re: No Access to MCC or shutdown

PostPosted: May 26th, '16, 22:18
by doktor5000
Please provide the output of the following commands, run as your regular user in a terminal:
Code: Select all
loginctl show-session $XDG_SESSION_ID
ps -ef|grep -v grep|grep -iE "polkit|policykit"
pkexec whoami     # you need to enter your root password when asked by the authentication dialog
echo $DISPLAY

and as root from:
Code: Select all
systemctl status polkit.service -a

Re: No Access to MCC or shutdown

PostPosted: May 27th, '16, 18:42
by Garthhh
Code: Select all
[logar@localhost ~]$ loginctl show-session $XDG_SESSION_ID
Id=c1
Name=logar
Timestamp=Thu 2016-05-26 08:45:25 PDT
TimestampMonotonic=37963474
VTNr=2
Display=:0
Remote=no
Service=kdm
Scope=session-c1.scope
Leader=1007
Audit=0
Type=x11
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
[logar@localhost ~]$ ps -ef|grep -v grep|grep -iE "polkit|policykit"
polkitd   2087     1  0 May26 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
[logar@localhost ~]$ pkexec whoami     # you need to enter your root password when asked by the authentication dialog
==== AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/usr/bin/whoami' as the super user
Authenticating as: root
Password:
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
[logar@localhost ~]$ su
Password:
[root@localhost logar]# systemctl status polkit.service -a
● polkit.service - Authorization Manager
   Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
   Active: active (running) since Thu 2016-05-26 08:45:32 PDT; 24h ago
     Docs: man:polkit(8)
 Main PID: 2087 (polkitd)
   CGroup: /system.slice/polkit.service
           └─2087 /usr/lib/polkit-1/polkitd --no-debug

May 26 08:45:32 localhost polkitd[2087]: Started polkitd version 0.113
May 26 08:45:32 localhost polkitd[2087]: Loading rules from directory /etc/polkit-1/rules.d
May 26 08:45:32 localhost polkitd[2087]: Loading rules from directory /usr/share/polkit-1/rules.d
May 26 08:45:32 localhost polkitd[2087]: Finished loading, compiling and executing 5 rules
May 26 08:45:32 localhost polkitd[2087]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
May 27 09:41:06 localhost polkitd[2087]: Registered Authentication Agent for unix-process:6460:8977234 (system bus name :1.51 [pkexec whoami], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 27 09:41:17 localhost polkitd[2087]: Operator of unix-process:6460:8977234 FAILED to authenticate to gain authorization for action org.freedesktop.policykit.exec for unix-process:6460:8977234 [/bin/bash] (owned by unix-user:logar)
May 27 09:41:17 localhost polkitd[2087]: Unregistered Authentication Agent for unix-process:6460:8977234 (system bus name :1.51, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
[root@localhost logar]#

Re: No Access to MCC or shutdown

PostPosted: May 27th, '16, 18:53
by doktor5000
Garthhh wrote:[logar@localhost ~]$ ps -ef|grep -v grep|grep -iE "polkit|policykit"
polkitd 2087 1 0 May26 ? 00:00:00 /usr/lib/polkit-1/polkitd --no-debug
[logar@localhost ~]$


There's no polkit user agent running, hence you won't get the authentication dialog and hence nothing happens.

You'd probably need to switch to a different polkit agent, but I'd need to look that up first and verify that it's working.
In the meantime you could try to reboot and check the output of ps -ef|grep -v grep|grep -iE "polkit|policykit" again to see whether a polkit agent is running, apart from the polkit system daemon /usr/lib/polkit-1/polkitd.

Re: No Access to MCC or shutdown

PostPosted: May 28th, '16, 19:16
by Garthhh
switching to mate de brought back functionality
I reenabled autologin to KDE & broke it again
except now I can't change back to mate
what commands will disable auto login or change de to mate?

Re: No Access to MCC or shutdown

PostPosted: May 28th, '16, 22:08
by doktor5000
Just change to which desktop you autologin via http://doc.mageia.org/mcc/5/en/content/drakboot.html

Re: No Access to MCC or shutdown

PostPosted: May 30th, '16, 16:24
by Garthhh
no drakboot. no policykit
Code: Select all
[logar@localhost ~]$ drakboot
==== AUTHENTICATING FOR org.mageia.drakboot.pkexec.run ===
Authentication is required to run Mageia Boot Configuration
Authenticating as: root
Password:
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
[logar@localhost ~]$

Re: No Access to MCC or shutdown

PostPosted: May 30th, '16, 18:42
by doktor5000
You'd need to change to root before you run drakboot via
Code: Select all
su -

Re: No Access to MCC or shutdown

PostPosted: May 31st, '16, 17:59
by Garthhh
thank thats good
how do I go about fixing the kde policy kit malfunction?

Re: No Access to MCC or shutdown

PostPosted: May 31st, '16, 18:11
by doktor5000
doktor5000 wrote:You'd probably need to switch to a different polkit agent, but I'd need to look that up first and verify that it's working.
In the meantime you could try to reboot and check the output of ps -ef|grep -v grep|grep -iE "polkit|policykit" again to see whether a polkit agent is running, apart from the polkit system daemon /usr/lib/polkit-1/polkitd.

Re: No Access to MCC or shutdown

PostPosted: May 31st, '16, 19:57
by Garthhh
Code: Select all
[logar@localhost ~]$ ps -ef|grep -v grep|grep -iE "polkit|policykit"
polkitd   1995     1  0 10:52 ?        00:00:00 /usr/lib/polkit-1/polkitd --no-debug
[logar@localhost ~]$

Re: No Access to MCC or shutdown

PostPosted: Aug 19th, '16, 01:34
by zeebra
Garthhh wrote:thank thats good
how do I go about fixing the kde policy kit malfunction?


Most likely by replacing it. I also had a similar polkit issue. In my case seemingly self created issue.

Solved it by clearing and replacing all polkit packages:

Code: Select all
urpmi --replacepkgs --clean lib64mate-polkit1_0 lib64polkit-gir1.0 lib64polkit-qt-agent-1_1 lib64polkit-qt-core-1_1 lib64polkit1_0 mate-polkit polkit polkit-kde-agent-1