Xfce policykit agent gdbus error org

Xfce Forum Sub domains You are not logged in. #1 2018-07-11 15:19:30 problems starting gparted I just installed gparted using the terminal to download the package by executing the command after it installed I then went to the Applications Folder and also used the Application Finder to locate and run the program from a […]

Содержание

  1. Xfce Forum
  2. #1 2018-07-11 15:19:30
  3. problems starting gparted
  4. #2 2018-07-11 16:20:43
  5. Re: problems starting gparted
  6. #3 2018-07-11 17:40:21
  7. Re: problems starting gparted
  8. #4 2018-07-11 20:14:27
  9. Re: problems starting gparted
  10. #5 2019-03-22 15:06:22
  11. Re: problems starting gparted
  12. Debian User Forums
  13. GDBus Error [Solved]
  14. GDBus Error [Solved]
  15. Re: GDBus Error
  16. Re: GDBus Error
  17. Re: GDBus Error
  18. Re: GDBus Error
  19. Re: GDBus Error
  20. Re: GDBus Error
  21. Re: GDBus Error [Solved]
  22. Re: GDBus Error [Solved]
  23. How to fix GDBus Error org freedesktop PolicyKit1 Error Failed An authentication agent already exists for the given subject error in Kali, LMDE or Debian Linux?
  24. How to fix GDBus Error org freedesktop PolicyKit1 Error Failed
  25. Background:
  26. Conclusion
  27. Check Also
  28. How to install VirtualBox Guest Additions in Kali Linux (Kali Rolling / Kali Linux 2016.2 / Kali 2017)
  29. Cracking password in Kali Linux using John the Ripper
  30. 5 comments
  31. Arch Linux
  32. #1 2021-03-20 17:50:03
  33. GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed
  34. #2 2021-03-20 17:51:54
  35. Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed
  36. #3 2021-03-20 18:19:05
  37. Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed
  38. #4 2021-03-20 18:30:18
  39. Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed
  40. #5 2021-03-21 13:04:45
  41. Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed
  42. #6 2021-03-23 11:31:28
  43. Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed
  44. #7 2021-06-08 18:15:00
  45. Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed
  46. Debian User Forums
  47. Problem with Policykit
  48. Problem with Policykit

Xfce Forum

Sub domains

You are not logged in.

#1 2018-07-11 15:19:30

problems starting gparted

I just installed gparted using the terminal to download the package by executing the command

after it installed I then went to the Applications Folder and also used the Application Finder to locate and run the program from a GUI.
After selecting the file and then clicking the launch button. nothing happens.
When I open the terminal and entered the command

I was asked to enter in my user password.

Upon entering my password I then received this error message:

Does anyone have any idea why it’s asking for my user password and then saying

and why it won’t open after clicking the launch
button from within the Application Menu?
This is what I get if I enter the command:

and the program still refuses to launch??

here is my os version:

Last edited by dlwilson88 (2018-07-11 15:29:22)

#2 2018-07-11 16:20:43

Re: problems starting gparted

I believe there is an active bug report about this issue (authentication not working without a Gui agent). Make sure you have a policykit agent installed and running. For ubuntu, I believe its in the «policykit-1-gnome» package and the authentication agent is «/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1».

If it’s not currently running, start it up and try again. If it works, check that it’s enabled in Settings Manager > Session and Startup > Startup Applications.

#3 2018-07-11 17:40:21

Re: problems starting gparted

Not sure what this output means?

Any idea why all or most all of the files failed to download? Should I try getting a tar.gz or some version
of a physical copy of the actual file? Or does the failed apt-get update mean there is an issue with my operating system?

#4 2018-07-11 20:14:27

Re: problems starting gparted

Temporary failure resolving ‘archive.ubuntu.com’

Is everything okay with your network connection? Can you connect to: http://archive.ubuntu.com/ubuntu/dists/?

#5 2019-03-22 15:06:22

Re: problems starting gparted

I had a similar problem on a fresh install of Ubuntu 18.04 after installing xfce4.

The problem was evident as en error message when trying run ‘Language Support’ (gnome-language-selector) after install.

No PolicyKit Authentication Agent was installed — or at least not one that xfce seemed to recognise.

I solved the problem by installing one:

$ sudo apt install policykit-1-gnome

That installed the package: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1.

It seemed to update the autostart list.

Though there is such a thing as ‘xfce-polkit’ and ‘xfce-polkit-git’, I could not see them on my machine and Debian [reports][3], in it’s account of the package policykit-1-gnome, that xfce still uses the gnome polkit agent:

«This implementation was originally designed for GNOME 2, but most GNOME-based desktop environments, including GNOME 3, GNOME Flashback, and MATE, have their own built-in PolicyKit agents and no longer use this one. The remaining users of this implementation are Cinnamon, XFCE and Unity.»

It is worth noting that the terminal emulator that comes default in Ubuntu and is still default after installing xfce (gnome terminal) would not run polkit-gnome-authentication-agent-1 after install. I understand it may have been necessary, perhaps ironically, to run it an an xterm. I didn’t attempt this. But all was well after restart.

Источник

Debian User Forums

GDBus Error [Solved]

GDBus Error [Solved]

#1 Post by larry77 » 2013-01-19 10:32

Dear All,
I use gdm3+XFCE on my box (amd64, debian testing).
Recently, when I start my XFCE session, I have been getting this error message

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject

Even starting a new XFCE session will not help. So far, it looks that this error message has no consequences, but it is annoying. any idea about how to fix it?
Cheers

Re: GDBus Error

#2 Post by llivv » 2013-01-19 11:38

I’m not sure what conflict Policy-kit is complaining about.

What I would try is after booting up the machine,
«shutdown gdm3» and then «start xfce» manually.
Double checking if Policy-kit still complains.

The following is how I would do the steps above:
At the gdm3 login screen

Re: GDBus Error

#3 Post by larry77 » 2013-01-19 12:23

Thanks a lot!
Unfortunately, both your procedure and logging in as a new user do not help.
It is not a big deal right now, but I am concerned I may have some troubles in the future.
I have no idea about how to troubleshoot this, so any help is appreciated.

Re: GDBus Error

#4 Post by llivv » 2013-01-19 12:43

its a new one on me too so if you’re patient with me guessing a lot I try to help OK

Describe where this error shows up? Like in a popup message on the xfce desktop?

Also do you have contrib and non-free enabled in your sources.list?

Are you running a full xfce Desktop? ie: all/most of the xfce packages?

Re: GDBus Error

#5 Post by larry77 » 2013-01-19 12:47

llivv wrote: its a new one on me too so if you’re patient with me guessing a lot I try to help OK

Describe where this error shows up? Like in a popup message on the xfce desktop??

Also do you have contrib and non-free enabled in your sources.list?

Are you running a full xfce Desktop? ie: all/most of the xfce packages?

Re: GDBus Error

#6 Post by llivv » 2013-01-19 12:54

Re: GDBus Error

#7 Post by larry77 » 2013-01-19 13:54

Hello,
I reinstalled those packages, removed a similar policy package for LXDE and saved a new XFCE session.
So far the annoying popup has disappeared and problem solved! Will post again in case it should reappear.
Thanks!

Re: GDBus Error [Solved]

#8 Post by ivorscott » 2013-12-14 19:46

This didn’t work for me.
My Solution ended up being this:

sudo apt-get purge lxpolkit
sudo reboot

Re: GDBus Error [Solved]

#9 Post by epp » 2015-04-26 18:25

I added wheezy-backports then installed the MATE desktop from it.

At each login, I see the same error:

I ran this text verbatim, through some search engines and in addition to a Red Hat bug report (on LXDE, marked WONTFIX), it indicated there may be more than one PolicyKit installed. One solution that claimed to have worked, was to uncheck the LXDE PolicyKit box in the MATE Desktop Session Settings. I did this, and the error continued to appear. There is a separate PolicyKit for MATE under the desktop session settings and tried that with both the MATE PolicyKit checked and unchecked. Again, the error continued to appear.

Источник

How to fix GDBus Error org freedesktop PolicyKit1 Error Failed An authentication agent already exists for the given subject error in Kali, LMDE or Debian Linux?

This is a small guide on How to fix GDBus Error org freedesktop PolicyKit1 Error Failed : An authentication agent already exists for the given subject error in Kali, LMDE or Debian Linux.

How to fix GDBus Error org freedesktop PolicyKit1 Error Failed

Background:

I use gdm3+XFCE on my box (amd64, Kali Linux). When I start my XFCE session, I have been getting this error message

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject

Even starting a new XFCE session will not help. So far, it looks that this error message has no consequences, but it is annoying. I found a way to fix this, sharing for interested readers.

Screenshots were taken from Kali Linux

I am using XFCE desktop/window manager.

To fix this go to Application Menu > Settings > Session and Startup >

Now un-check LXPolkit from Application Autostart tab. Click on Close.

That’s it, you won’t see that error message again.

Conclusion

GDBus Error org freedesktop PolicyKit1 Error Failed is a common issue in many Linux Operating systems which is not just limited to Kali Linux or Debian Linux.

I cannot say if my fix will apply to every situation, but it seems to work for me and my friends.

Thanks for reading. Please share.

Check Also

How to install VirtualBox Guest Additions in Kali Linux (Kali Rolling / Kali Linux 2016.2 / Kali 2017)

Since Kali Linux 2016 came out (also known as Kali Rolling), it seems that Official …

Cracking password in Kali Linux using John the Ripper

John the Ripper is a free password cracking software tool. Initially developed for the Unix …

Thanks: I installed XFCE over LXDE w/o reformatting (desiring to keep my /HOME folder). LXDE still shows up as a Login option, as well. Really, I should back up my home folder to this new USB stub I have in front of myself and reformat, first. (Really, I should get my lifestyle into a manner where I may purchase an old Italian villa–thus being able to recline and eat with friends–always poking verbal holes into politicians, while servants busily fan all of us with huge fronds–enjoying life as a carefree (and, careless) patrician Roman might! OK–something spiritual nudged me and chided a few moments ago!: Just now, I opened the package for the stub!)

Источник

Arch Linux

You are not logged in.

#1 2021-03-20 17:50:03

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed

I’ve just updated, and after the update when I tried to access folders in my GUI file manager (nautilus) with root access (by adding admin:// to the front of the path), I get GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does not have uid set
I tried to search online, it seems that this message isn’t something that has really occurred that often to anyone at all. I’m at a loss. I loaded a snapshot I made 2 weeks ago and it is fine, then I updated again and then it broke again. It must be something that happens during the update that breaks that access. Anyone have similar problems?

#2 2021-03-20 17:51:54

Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed

Just tried it on my laptop and got the same thing

#3 2021-03-20 18:19:05

Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed

I can confirm the behaviour. Probably caused by the recent gvfs update.

The terminal shows

#4 2021-03-20 18:30:18

Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed

Yep, I just updated again but ignored all updates from gvfs packages, and it is indeed not broken.

#5 2021-03-21 13:04:45

Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed

I’m also seeing the same thing. I’ve reporting as a bug so it can be tracked (https://bugs.archlinux.org/task/70108), then I might try digging through the gvfs repo.

Reverting just that one commit reverts the behaviour (below). However, there could be some other issue that’s preventing this change from working as expected.

Last edited by jonathon (2021-03-21 14:34:40)

#6 2021-03-23 11:31:28

Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed

Also having this issue. I noticed if I do upgrade the gvfs* packages to 1.48.0-2, I get an «Unable to handle admin: locations» error. Then after downgrading to the 2 cached versions(1.46.2-1 and 1.48.0-1), I get this same GDBus.Error. I’m curious. What other packages could’ve caused this change since it seems to happen with gvfs updated or not? I could check my log and play whack-a-mole, but unsure if that would even solve it.

EDIT: Apologies, Downgrading to 1.46.2-1 again today seemed to have worked. Unsure what happened with the downgrade yesterday that it didn’t. But user error apparently.

Last edited by gdi (2021-03-24 14:12:36)

#7 2021-06-08 18:15:00

Re: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed

Does anyone know if there’s an open issue somewhere on this? It doesn’t seem clearly proven in this thread that this is upstream. Hmm what to do. I use Xfce and now Thunar won’t even start up because of this error:

Источник

Debian User Forums

Problem with Policykit

Problem with Policykit

#1 Post by marc1uk » 2014-09-06 22:16

After recently removing gdm3 I’ve found that I can no longer shut-down/restart from the menu, mount disks in thunar, run synaptic from the start menu, along with a bunch of other things.
I’ve tracked down the problem to a failure to start a policykit agent; this happens with both policykit-1-gnome and lxpolkit. The following errors show up in my .xsession-errors file, or are returned if I try to start the agent from terminal:

«** (lxpolkit:2463): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine session the caller is in»
when using lxpolkit, or
«(polkit-gnome-authentication-agent-1:2542): polkit-gnome-1-WARNING **: Unable to determine the session we are in: No session for pid 2542»
when using polkit-gnome-1

I’ve found a number of threads on this problem, with the most extensive being this launchpad bug: https://bugs.launchpad.net/ubuntu/+sour . ug/1240336.

That seems to contain most of the solutions I’ve found elsewhere, but unfortunately none of them work for me. I’m starting xfce4 from the console with ‘startx’ — I have:

    no .xinitrc, have «exec ck-launch-session startxfce4» in

/.xsession, and have «session optional pam_loginuid.so» in /etc/pam.d/common-session, as per https://wiki.debian.org/Xfce

do have usisks, consolekit, policykit-1-gnome/lxpolkit installed

polkit-gnome-authentication-agent-1 or lxpolkit are in startup services

a policykit trial from terminal ( pkexec echo «test» ) asks for password and behaves as expected

in my /etc/pam.d/common-session

Have also tried with ‘required’ instead of optional (couldn’t startx after that)

to /etc/polkit-1/localauthority/50-local.d/networkmanager.pkla so far appears to be the only thing that has worked, which has granted me the infinitely useful ability to turn off networking from the panel.

my ck-list-sessions shows both active=TRUE and is-local=TRUE:

downgraded libpolkit-gobject-0-1 and libpolkit-agent-0-1 to version 0.105-3 as per https://bugs.debian.org/cgi-bin/bugrepo . bug=738023

Basically I’ve just given everything I can find a shot.

Can someone assist in a more systematic approach?

Источник

November 19, 2013
How to, Kali Linux, Linux

This is a small guide on How to fix GDBus Error org freedesktop PolicyKit1 Error Failed : An authentication agent already exists for the given subject error in Kali, LMDE or Debian Linux.

How to fix GDBus Error org freedesktop PolicyKit1 Error Failed

Background:

I use gdm3+XFCE on my box (amd64, Kali Linux). When I start my XFCE session, I have been getting this error message

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject

Even starting a new XFCE session will not help. So far, it looks that this error message has no consequences, but it is annoying. I found a way to fix this, sharing for interested readers.

Screenshots were taken from Kali Linux

root@kali:~# lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Debian GNU/Linux Kali Linux 1.0
Release:    Kali Linux 1.0
Codename:    n/a
root@kali:~#

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed - blackMORE Ops

I am using XFCE desktop/window manager.

To fix this go to Application Menu > Settings > Session and Startup >

Fixing GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed - blackMORE Ops

Now un-check LXPolkit from Application Autostart tab. Click on Close.

Uncheck LXPolkit - GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed - blackMORE Ops

That’s it, you won’t see that error message again.

Conclusion

GDBus Error org freedesktop PolicyKit1 Error Failed is a common issue in many Linux Operating systems which is not just limited to Kali Linux or Debian Linux.

  1. GDbus Error org openobex Error Failed: Unable to request session problem
  2. Problem installing .deb files on Wheezy
  3. gnome-shell:oh no something has gone wrong error
  4. Bug 657006 – GDBus Error org freedesktop PolicyKit1 Error Failed: An authentication agent already exists for the given subject
  5. Raspberry Pi error
  6. GDBus Error org freedesktop PolicyKit1 Error Failed An authentication agent already exists for the given subject
  7. GDBus Error org openobex Error Failed Unable to request session
  8. Error GDBus Error org freedesktop DBus Error Spawn ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
  9. MATE-Desktop for fedora
  10. Bug#687844: debian-policy: GDBus Error org freedesktop PolicyKit1 Error Failed:
  11. Installing Nessus in Kali Linux
  12. I am kali linx user i hv some problm when i install any type of software app in my kali linux this error show GDBus Error org gtk GDBus Un?
  13. GDBus Error org gtk GDBus UnmappedGError Quark._pk_5ftransaction_5ferror.Code4: SimulateInstallFiles not supported by backend
  14. Debian Bug report logs – #703016 policykit-1-gnome: polkit-gnome-authentication-agent-1 fails to start
  15. Small problem with the version of Mate ..

I cannot say if my fix will apply to every situation, but it seems to work for me and my friends.

Thanks for reading. Please share.

Check Also

Cracking password using John the Ripper in Kali Linux - blackMORE Ops

Cracking password in Kali Linux using John the Ripper

John the Ripper is a free password cracking software tool. Initially developed for the Unix …


Description


Brian J. Murrell



2013-10-29 15:00:08 UTC

+++ This bug was initially created as a clone of Bug #657006 +++

Description of problem:

During login to the MATE desktop this error pops up:

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Install F19
2. Add the MATE yum group
3. Log out and log backk in to MATE desktop
  
Actual results:
You will get a dialog with the above error

Expected results:
No dialog

Additional info:

I noticed that this error is coming from lxpolkit.  When I acknowledge the dialog, lxpolkit process goes away.

lxpolkit was added by the MATE yum group.

--- Additional comment from Reilly Hall on 2010-12-11 12:17:51 EST ---

I am getting this same error on one of my systems that too is running Fedora 14 x64 LXDE.  I would be willing to provide more information if requested.

--- Additional comment from Dan O'Brien on 2010-12-11 12:27:42 EST ---

Is this bug dead?  I've seen no follow up whatsoever.  And I'm still getting this error as is this other commenter.  HELLO. IS THIS THING ON?

--- Additional comment from Richard Shaw on 2010-12-14 21:01:27 EST ---

I'm getting the same error on two F14 x86_64 installs.

--- Additional comment from Richard Shaw on 2010-12-14 21:02:02 EST ---



--- Additional comment from Richard Shaw on 2010-12-15 09:31:18 EST ---

I believe this was caused during an update and is not isolated to F14. I used LXDE as my desktop for my MythTV machine and I remember seeing an error like this pop-up at some point on F13 x86_64. I can't be sure if it was the exact same error as the system auto-started Myth and I never investigated it further since I was already planning a fresh install of F14.

--- Additional comment from Richard Shaw on 2011-01-03 13:41:08 EST ---

I think I found the problem. The solution is so go into "Preferences->Desktop Session Settings" and un-check "PolicyKit Authentication Agent" as LXDE runs it's own LXPolKit Authentication Agent.

--- Additional comment from Till Bubeck on 2011-01-04 02:38:06 EST ---

I can confirm, that the alert box is not shown anymore with the fix from comment #6. Additionally I do not see anything broken by disabling the PolicyKit Authentication Agent.

Thanks!

--- Additional comment from Richard Shaw on 2011-01-04 08:51:20 EST ---

I'm out of my league here but I'll ask a few questions...

Are the session "services" (for lack of a better description) DE dependent? If so, then I think PolicyKit Auth. Agent should be disabled for LXDE by default.

--- Additional comment from Christoph Wickert on 2011-01-08 06:13:08 EST ---

We need an agent but it does not matter which one this it. IMHO each desktop environment should use it's own default agent. The problem is that /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop only contains "NotShowIn=KDE;" and lacks "LXDE".

I already suggested that change back in April 2010 on the desktop-mailing list [1] but the GNOME maintainers refused. Instead they suggested to hardcode the agent somewhere. This was part of the "PolkitAgentReorg" feature [2] that never happened.

IMHO this feature is useless: People should be free to use whatever agent they want. They still might want to use polkit-gnome in LXDE because it has more features (but also more dependencies). Xfce doesn't have xfce4-polkit or alike. We should not and we cannot decide for the users, we should focus on providing a reasonable default configuration that works out of the box and does not throw errors.

David, does that sound reasonable? Can I go ahead and make that NotShowIn change in polkit-gnome?

What I'd like to know from all you bug reporters: Is there anybody who did a fresh install of Fedora 14 or installed the F14 LXDE spin or did you all upgrade? If you upgraded, polkit-gnome was already installed and lxpolkit was installed in addition to it because it is a new package in F14. If you did a fresh install lxpolkit should have fulfilled the requirement for "PolicyKit-authentication-agent" (a virtual provides that is provided by lxpolkit, polkit-gnome and kdebase), so polkit-gnome should not have been pulled in. Something might have an explicit requirement for one or the other agent hardcoded, this would be a bug in packaging but then.

Last but not least I'd like to invite all LXDE users to join our Fedora LXDE mailing list at http://lists.fedoraproject.org/pipermail/lxde/
This is the right place to talk about issues like this one. I just found this bug by accident.

[1] http://lists.fedoraproject.org/pipermail/desktop/2010-April/006091.html
[2] http://fedoraproject.org/wiki/Features/PolkitAgentReorg

--- Additional comment from Dan O'Brien on 2011-01-08 08:05:30 EST ---

I did a fresh install of the F14 LXDE (64 bit) and encountered this problem.

--- Additional comment from Christoph Wickert on 2011-01-08 08:35:57 EST ---

OK, in order to find out what pulled in polkit-gnome
- please try to uninstall it with yum. If there are no deps and it will uninstall, you don't need to confirm. If there are deps, please tell us.
- please attach the output of rpm -qa --last to this ticket

Thanks for your help.

--- Additional comment from Dan O'Brien on 2011-01-08 08:43:34 EST ---

/home/dmobrien: rpm -q polkit-gnome
polkit-gnome-0.97-4.fc14.x86_64
/home/dmobrien: sudo rpm -e polkit-gnome
error: Failed dependencies:
	PolicyKit-gnome is needed by (installed) blueman-1.21-6.fc14.x86_64
	polkit-gnome is needed by (installed) gnome-session-2.32.0-1.fc14.x86_64

--- Additional comment from Dan O'Brien on 2011-01-08 08:44:18 EST ---

my rpm -qa --last listing

--- Additional comment from Till Bubeck on 2011-01-08 09:05:28 EST ---

I also did a fresh install from standard FC14 DVD and afterwards did a "yum groupinstall LXDE".

--- Additional comment from Christoph Wickert on 2011-01-08 09:46:53 EST ---

Thanks for the feedback.

(In reply to comment #12)
>  PolicyKit-gnome is needed by (installed) blueman-1.21-6.fc14.x86_64

filed as bug 668157

>  polkit-gnome is needed by (installed) gnome-session-2.32.0-1.fc14.x86_64

filed as bug 668156

--- Additional comment from  on 2011-02-13 13:24:32 EST ---

I did as in comment 6 and 7 thanks guys it worked

--- Additional comment from Dan O'Brien on 2011-02-13 15:08:42 EST ---

I do 6 but it keeps coming back set.

--- Additional comment from Christoph Wickert on 2011-02-13 15:38:12 EST ---

Please give me the output of 
cat ~/.config/autostart/lxpolkit.desktop and
cat ~/.config/autostart/polkit-gnome-authentication-agent-1.desktop

--- Additional comment from Christoph Wickert on 2011-02-13 15:47:50 EST ---

I have filed bug 657006 against polkit-gnome now.

--- Additional comment from Dan O'Brien on 2011-02-13 18:47:42 EST ---

/home/dmobrien: cat ~/.config/autostart/lxpolkit.desktop
cat: /home/dmobrien/.config/autostart/lxpolkit.desktop: No such file or directory
/home/dmobrien: cat ~/.config/autostart/polkit-gnome-authentication-agent-1.desktop
[Desktop Entry]
Name=PolicyKit Authentication Agent
Name[ar]=مدير الاستيثاق PolicyKit
Name[be]=PolicyKit - аґент аўтэнтыфікацыі
Name[bn_IN]=PolicyKit অনুমোদনের এজেন্ট
Name[ca]=Agent d'autenticació del PolicyKit
Name[cs]=Ověřovací agent PolicyKit
Name[da]=Godkendelsesprogrammet PolicyKit
Name[de]=Legitimationsdienst von PolicyKit
Name[el]=Πράκτορας πιστοποίησης PolicyKit
Name[en_GB]=PolicyKit Authentication Agent
Name[es]=Agente de autenticación de PolicyKit
Name[eu]=PolicyKit autentifikatzeko agentea
Name[fi]=PolicytKit-tunnistautumisohjelma
Name[fr]=Agent d'authentification de PolicyKit
Name[gl]=Axente de autenticación PolicyKit
Name[gu]=PolicyKit સત્તાધિકરણ એજન્ટ
Name[hi]=PolicyKit प्रमाणीकरण प्रतिनिधि
Name[hu]=PolicyKit hitelesítési ügynök
Name[it]=Agente di autenticazione per PolicyKit
Name[ja]=PolicyKit 認証エージェント
Name[kn]=PolicyKit ದೃಢೀಕರಣ ಮಧ್ಯವರ್ತಿ
Name[lt]=PolicyKit tapatybės nustatymo agentas
Name[ml]=പോളിസിക്കിറ്റ് ഓഥന്റിക്കേഷന്‍ ഏജന്റ്
Name[mr]=PolicyKit ऑथेंटीकेशन एजेंट
Name[or]=PolicyKit ବୈଧିକରଣ ସଦସ୍ୟ
Name[pa]=ਪਾਲਸੀਕਿੱਟ ਪਰਮਾਣਕਿਤਾ ਏਜੰਟ
Name[pl]=Agent uwierzytelniania PolicyKit
Name[pt]=Agente de Autenticação PolicyKit
Name[pt_BR]=Agente de autenticação PolicyKit
Name[sl]=PolicyKit program overjanja
Name[sv]=Autentiseringsagent för PolicyKit
Name[ta]=PolicyKit அங்கீகார முகவர்
Name[te]=పాలసీకిట్ ధృవీకరణ ప్రతినిధి
Name[th]=ตัวกลางสำหรับยืนยันตัวบุคคล PolicyKit
Name[uk]=Агент автентифікації PolicyKit
Name[zh_CN]=PolicyKit 认证代理
Name[zh_HK]=PolicyKit 驗證代理程式
Name[zh_TW]=PolicyKit 驗證代理程式
Comment=PolicyKit Authentication Agent
Comment[ar]=مدير الاستيثاق PolicyKit
Comment[be]=PolicyKit - аґент аўтэнтыфікацыі
Comment[bn_IN]=PolicyKit অনুমোদনের এজেন্ট
Comment[ca]=Agent d'autenticació del PolicyKit
Comment[cs]=Ověřovací agent PolicyKit
Comment[da]=Godkendelsesprogrammet PolicyKit
Comment[de]=Legitimationsdienst von PolicyKit
Comment[el]=Πράκτορας πιστοποίησης PolicyKit
Comment[en_GB]=PolicyKit Authentication Agent
Comment[es]=Agente de autenticación de PolicyKit
Comment[eu]=PolicyKit autentifikatzeko agentea
Comment[fi]=PolicytKit-tunnistautumisohjelma
Comment[fr]=Agent d'authentification de PolicyKit
Comment[gl]=Axente de autenticación PolicyKit
Comment[gu]=PolicyKit સત્તાધિકરણ એજન્ટ
Comment[hi]=PolicyKit प्रमाणीकरण प्रतिनिधि
Comment[hu]=PolicyKit hitelesítési ügynök
Comment[it]=Agente di autenticazione per PolicyKit
Comment[ja]=PolicyKit 認証エージェント
Comment[kn]=PolicyKit ದೃಢೀಕರಣ ಮಧ್ಯವರ್ತಿ
Comment[lt]=PolicyKit tapatybės nustatymo agentas
Comment[ml]=പോളിസിക്കിറ്റ് ഓഥന്റിക്കേഷന്‍ ഏജന്റ്
Comment[mr]=PolicyKit ऑथेंटीकेशन एजेंट
Comment[or]=PolicyKit ବୈଧିକରଣ ସଦସ୍ୟ
Comment[pa]=ਪਾਲਸੀਕਿੱਟ ਪਰਮਾਣਕਿਤਾ ਏਜੰਟ
Comment[pl]=Agent uwierzytelniania PolicyKit
Comment[pt]=Agente de Autenticação PolicyKit
Comment[pt_BR]=Agente de autenticação PolicyKit
Comment[sl]=PolicyKit program overjanja
Comment[sv]=Autentiseringsagent för PolicyKit
Comment[ta]=PolicyKit அங்கீகார முகவர்
Comment[te]=పాలసీకిట్ ధృవీకరణ ప్రతినిధి
Comment[th]=ตัวกลางสำหรับยืนยันตัวบุคคล PolicyKit
Comment[uk]=Агент автентифікації PolicyKit
Comment[zh_CN]=PolicyKit 认证代理
Comment[zh_HK]=PolicyKit 驗證代理程式
Comment[zh_TW]=PolicyKit 驗證代理程式
Exec=/usr/libexec/polkit-gnome-authentication-agent-1
Terminal=false
Type=Application
Categories=
NoDisplay=true
X-Desktop-File-Install-Version=0.16
NotShowIn=KDE;LXDE;
/home/dmobrien:

--- Additional comment from Susi Lehtola on 2011-05-06 12:45:58 EDT ---

I just got the same error in XFCE4 on a fresh install of F15.

--- Additional comment from Christoph Wickert on 2011-05-21 14:35:27 EDT ---

Can you give us more details, Jussi? What polkit agents do ypu have installed and which are running? Is gnome-shell installed? It ships yet another agent.

--- Additional comment from Gilboa Davara on 2011-05-27 10:37:48 EDT ---

Seeing the same with Fedora 15 / x86_64 / XFCE installed.
gnome-shell installed.
How can I check which polkit agents are active?

--- Additional comment from Christoph Wickert on 2011-05-27 10:47:34 EDT ---

Look at the files in /etc/xdg/autostart or ~/.config/autostart. 'ps -A| grep pol' also helps but I have no idea how the new agent that is included in gnome-shell is called.

--- Additional comment from Gilboa Davara on 2011-05-27 10:57:40 EDT ---

OK. I looked the xfce startup configuration and it had two polkit agents: LXPolKit and PolicyKit.

Disabling LXPolKit solved the problem.

--- Additional comment from Jos Vos on 2011-09-08 12:26:10 EDT ---

Where did you find this?  On F15 with all updates (and GNOME / LXE / Xfce installed) I get this error on every Xfce session.

--- Additional comment from Christoph Wickert on 2011-09-08 13:09:30 EDT ---

In the session properties. For LXDE this is lxsession-edit, for Xfce it is xfce4-session-settings and for GNOME is is in gnome-session-properties.

--- Additional comment from Jos Vos on 2011-09-12 09:38:23 EDT ---

OK, like Gilboa I had in my Xfce session autostart list both PolicyKit and LXPolKit enabled, so I disabled LXPolKit.

--- Additional comment from bob mckay on 2011-11-28 22:31:25 EST ---

Still present in F16. This is a bit of a disaster for server systems, because gnome and a lightweight such as lxde are both needed (most users seem to prefer gnome for local sessions; but in my experience gnome3 is pretty much unusable for remote sessions). Requiring users to disable a security feature (i.e. lxpolkit) seems to be asking for trouble down the line.

--- Additional comment from Christoph Wickert on 2011-11-29 03:35:00 EST ---

Bob, we are not asking anybody to disable a security feature but to decide which of the two programs that provide exactly the same functionality they want to use.

--- Additional comment from bob mckay on 2011-11-29 10:25:36 EST ---

Christoph, I know that's not what you're intending to do, and there's a strong possibility that I'm misunderstanding. But if people become accustomed to turning off lxpolkit on systems which have gnome installed, isn't there a high likelihood that they will think it is also the right thing to do on systems built with lxde only? And if the automatic loading of gnome-polkit ever gets disabled in a future version of fedora, won't the same problems arise even on systems built with gnome? My concern was that this falls into the human factors side of security, setting up a situation where users with limited knowledge are likely to default into unsafe practices.

--- Additional comment from Linux Zombie on 2012-01-11 12:18:38 EST ---

Long post incoming.. This really is an issue.  I created an account just to post this.  I've been scurrying the web off and on trying to find a solution to this.  I have done fresh installs of F16 but using Xfce (moved over from Ubuntu Unity = yuk).

Anyways, I can say that initially, it was working fine (fresh install) but at some point after installing other packages and updates, this broke.  Info:

- Fedora 16 Xfce spin 64-bit
- /etc/xdg/autostart/xfce-polkit-gnome-authentication-agent-1.desktop exists but not a ~/.config/... equivalent and contains:
    [Desktop Entry]
    Name=PolicyKit Authentication Agent
    ...
    Exec=/usr/libexec/polkit-gnome-authentication-agent-1
    Terminal=false
    Type=Application
    Categories=X-XFCE;
    NoDisplay=true
    X-Desktop-File-Install-Version=0.18
    OnlyShowIn=XFCE;
- gnome-shell is NOT installed
- ps -A | grep pol outputs processes: polkitd, polkit-gnome-au
- yum info polkit-gnome outputs:
    Loaded plugins: langpacks, presto, refresh-packagekit
    Installed Packages
    Name        : polkit-gnome
    Arch        : x86_64
    Version     : 0.104
    Release     : 2.fc16
    Size        : 356 k
    Repo        : installed
    From repo   : koji-override-0
    Summary     : PolicyKit integration for the GNOME desktop
- xfce4-session-settings does have the check mark for "Policy Kit Authentication Agent

Last to mention, I "do" run vncserver and remote X into the box.

This last piece "might" shed some light.  When I had a GUI session on the "head" and a vnc client separate remote X session.  The PolKit would popup the root password prompt on the MAIN head's GUI when it should be asking on the vnc client remote session!  However, I changed the run-time boot to just multi-user (no initial gui on the "head").. that seems to have solved the issue temporarily (started getting the polkit prompt in the vnc clients), but then this stopped working again.. even without a "head" GUI.

My workaround is to not use the GUI firewall, Add/Remove Software, Software Update, etc.  Been just opening up a term window, su, then use yum (and firewall-tui).

--- Additional comment from Linux Zombie on 2012-01-11 12:44:09 EST ---

my error's slightly different.  If I try to run system-config-firewall, I get:

"org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.firewall.auth: "

if I try to run gpk-application (Add/Remove Software), upon trying to install something, I get a slightly different error with this window:

"Authorization Failed - You have failed to provide correct authorization.  Please check any passwords or account settings."

before, I would get a prompt to enter the root password instead.

--- Additional comment from Fedora End Of Life on 2012-08-16 17:50:36 EDT ---

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from Peter H. Jones on 2013-07-29 17:21:58 EDT ---

Getting this bug in Fedora 19. Here is the message in /var/log/messages:

Jul 29 16:58:29 mariehe /etc/gdm/Xsession[1301]: ** (lxpolkit:1652): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject

Can't change Status or Version.


Comment 1


Wolfgang Ulbrich



2013-10-29 21:42:14 UTC

That's a bit weird because lxpolkit isn't in mate comps group.
Can you attach the yum log of the groupinstall command?
yum history
yum history list <id>

Can you uninstall lxpolkit without removing a mate package?


Comment 2


Wolfgang Ulbrich



2013-10-29 21:43:51 UTC

sorry,
yum history
yum history info <id>


Comment 3


Dan Mashal



2013-10-29 22:04:23 UTC

MATE does not install lxpolkit.

What DE did you have installed before you installed MATE?

What is the exact command you used to install mate?

What is the output of "repoquery --whatrequires lxpolkit"?


Comment 4


Brian J. Murrell



2013-10-30 03:02:04 UTC

Hrm.  So the things you gave me to investigate have shed some light.  I thought I was sure lxpolkit came with MATE but I was mistaken.  It seems to have come as a dependency of blueman:

$ repoquery --whatrequires lxpolkit
blueman-0:1.23-6.fc19.x86_64

which is a dependency of cinnamon:

$ repoquery --whatrequires blueman
blueman-nautilus-0:1.23-6.fc19.x86_64
bluez-0:4.101-6.fc19.x86_64
bluez-0:4.101-9.fc19.x86_64
cinnamon-0:2.0.3-1.fc19.x86_64

This dependency of cinnamon on blueman seemed to have happened when I got cinnamon-1.9.1-19.fc19.x86_64.

What is interesting though is that I was able to remove just lxpolkit and nothing else which is not surprising when you notice that blueman does not depend on lxpolkit:

$ rpm -q -R blueman
/bin/sh
/bin/sh
/bin/sh
/usr/bin/python
PolicyKit-authentication-agent
bluez >= 4.25
config(blueman) = 1.23-6.fc19
dbus
desktop-notification-daemon
gnome-python2-gconf
gnome-python2-gnome
gvfs-obexftp
libatk-1.0.so.0()(64bit)
libbluetooth.so.3()(64bit)
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libcairo.so.2()(64bit)
libdl.so.2()(64bit)
libfontconfig.so.1()(64bit)
libfreetype.so.6()(64bit)
libgdk-x11-2.0.so.0()(64bit)
libgdk_pixbuf-2.0.so.0()(64bit)
libgio-2.0.so.0()(64bit)
libglib-2.0.so.0()(64bit)
libgobject-2.0.so.0()(64bit)
libgthread-2.0.so.0()(64bit)
libgtk-x11-2.0.so.0()(64bit)
libm.so.6()(64bit)
libpango-1.0.so.0()(64bit)
libpangocairo-1.0.so.0()(64bit)
libpangoft2-1.0.so.0()(64bit)
libpthread.so.0()(64bit)
libpthread.so.0(GLIBC_2.2.5)(64bit)
libpython2.7.so.1.0()(64bit)
libstartup-notification-1.so.0()(64bit)
libutil.so.1()(64bit)
notify-python
obex-data-server >= 0.4.3
pulseaudio-libs-glib2
pygtk2 >= 2.12
python >= 2.5
python(abi) = 2.7
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
rpmlib(PayloadIsXz) <= 5.2-1

But then why does repoquery --whatrequires lxpolkit say blueman requires it?


Comment 5


Wolfgang Ulbrich



2013-10-30 09:07:00 UTC

You can savely remove blueman because it doesn't work anymore in f20.
Blueman isn't ported to bluez5 and upstream is death.
A alternative for mate user is to use bluedevil from kde.


Comment 6


Wolfgang Ulbrich



2013-10-30 09:31:04 UTC

Sorry, i missread your fedora version, blueman do work in f19.


Comment 7


Rex Dieter



2013-10-30 11:55:59 UTC

blueman Requires: PolicyKit-authentication-agent

which has multiple providers including lxpolkit, mate-polkit, gnome-polkit, kde-polkit

(not sure why repoquery doesn't list them all)


Comment 8


Michael Schwendt



2013-10-30 17:45:11 UTC

> But then why does repoquery --whatrequires lxpolkit say blueman requires it?

Because it defaults to enabling option --alldeps, which means it checks whether anything depends on stuff _provided by_ lxpolkit. Nothing requires the package name "lxpolkit":

  $ repoquery --exactdeps --whatrequires lxpolkit
  $

The dependency is only on the "PolicyKit-authentication-agent" capability of lxpolkit. 

  $ repoquery --whatrequires PolicyKit-authentication-agent
  blueman-0:1.23-7.fc20.x86_64

  $ repoquery --whatprovides PolicyKit-authentication-agent
  mate-polkit-0:1.6.0-2.fc20.x86_64
  mate-polkit-0:1.6.0-2.fc20.i686
  lxpolkit-0:0.1.0-6.fc20.x86_64
  polkit-gnome-0:0.105-5.fc20.x86_64
  polkit-kde-0:0.99.1-2.20130311git.fc20.x86_64

Compare with:

  $ repoquery --whatrequires polkit-gnome
  blueman-0:1.23-7.fc20.x86_64
  cinnamon-session-0:2.0.1-1.fc20.x86_64
  xfce4-session-0:4.10.1-2.fc20.i686
  xfce4-session-0:4.10.1-2.fc20.x86_64

  $ repoquery --exactdeps --whatrequires polkit-gnome
  cinnamon-session-0:2.0.1-1.fc20.x86_64
  xfce4-session-0:4.10.1-2.fc20.i686
  xfce4-session-0:4.10.1-2.fc20.x86_64

"blueman" is gone in the second query. The first query only found that polkit-gnome may resolve a "PolicyKit-authentication-agent" requirement.


> (not sure why repoquery doesn't list them all)

Because the query is specifically about what depends on lxpolkit.

User avatar

larry77

Posts: 569
Joined: 2006-09-24 17:59
Has thanked: 4 times
Been thanked: 1 time

GDBus Error [Solved]

#1

Post

by larry77 » 2013-01-19 10:32

Dear All,
I use gdm3+XFCE on my box (amd64, debian testing).
Recently, when I start my XFCE session, I have been getting this error message

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject

Even starting a new XFCE session will not help. So far, it looks that this error message has no consequences, but it is annoying….any idea about how to fix it?
Cheers

larry77

Last edited by larry77 on 2013-01-19 14:04, edited 1 time in total.


User avatar

llivv

Posts: 5484
Joined: 2007-02-14 18:10
Location: cold storage

Re: GDBus Error

#2

Post

by llivv » 2013-01-19 11:38

I’m not sure what conflict Policy-kit is complaining about.

What I would try is after booting up the machine,
«shutdown gdm3» and then «start xfce» manually.
Double checking if Policy-kit still complains.

The following is how I would do the steps above:
At the gdm3 login screen

at the console login screen
login as user then su to root or use sudo for the next command.

exit out of root and start xfce manually

or you could also try adding another user account and see if
you get the same error when logging in as a new user.

In memory of Ian Ashley Murdock (1973 — 2015) founder of the Debian project.


User avatar

larry77

Posts: 569
Joined: 2006-09-24 17:59
Has thanked: 4 times
Been thanked: 1 time

Re: GDBus Error

#3

Post

by larry77 » 2013-01-19 12:23

Thanks a lot!
Unfortunately, both your procedure and logging in as a new user do not help.
It is not a big deal right now, but I am concerned I may have some troubles in the future.
I have no idea about how to troubleshoot this, so any help is appreciated.

larry77


User avatar

llivv

Posts: 5484
Joined: 2007-02-14 18:10
Location: cold storage

Re: GDBus Error

#4

Post

by llivv » 2013-01-19 12:43

its a new one on me too so if you’re patient with me guessing a lot I try to help OK

Describe where this error shows up? Like in a popup message on the xfce desktop?

Also do you have contrib and non-free enabled in your sources.list?

Are you running a full xfce Desktop? ie: all/most of the xfce packages?

Last edited by llivv on 2013-01-19 12:49, edited 2 times in total.

In memory of Ian Ashley Murdock (1973 — 2015) founder of the Debian project.


User avatar

larry77

Posts: 569
Joined: 2006-09-24 17:59
Has thanked: 4 times
Been thanked: 1 time

Re: GDBus Error

#5

Post

by larry77 » 2013-01-19 12:47

llivv wrote:its a new one on me too so if you’re patient with me guessing a lot I try to help OK

Describe where this error shows up? Like in a popup message on the xfce desktop??

Precisely! It is a popup showing up after I login.

Also do you have contrib and non-free enabled in your sources.list?

Are you running a full xfce Desktop? ie: all/most of the xfce packages?

Yes again. I have enabled also contrib and non-free and I have pretty much the whole XFCE desktop installed.


User avatar

llivv

Posts: 5484
Joined: 2007-02-14 18:10
Location: cold storage

Re: GDBus Error

#6

Post

by llivv » 2013-01-19 12:54

see if you have either or both of these packages installed
policykit-1-gnome
policykit-1

In memory of Ian Ashley Murdock (1973 — 2015) founder of the Debian project.


User avatar

larry77

Posts: 569
Joined: 2006-09-24 17:59
Has thanked: 4 times
Been thanked: 1 time

Re: GDBus Error

#7

Post

by larry77 » 2013-01-19 13:54

Hello,
I reinstalled those packages, removed a similar policy package for LXDE and saved a new XFCE session.
So far the annoying popup has disappeared and problem solved! Will post again in case it should reappear.
Thanks!

Larry77



epp

Posts: 182
Joined: 2011-03-11 23:22
Has thanked: 1 time

Re: GDBus Error [Solved]

#9

Post

by epp » 2015-04-26 18:25

I added wheezy-backports then installed the MATE desktop from it.

At each login, I see the same error:

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject

I ran this text verbatim, through some search engines and in addition to a Red Hat bug report (on LXDE, marked WONTFIX), it indicated there may be more than one PolicyKit installed. One solution that claimed to have worked, was to uncheck the LXDE PolicyKit box in the MATE Desktop Session Settings. I did this, and the error continued to appear. There is a separate PolicyKit for MATE under the desktop session settings and tried that with both the MATE PolicyKit checked and unchecked. Again, the error continued to appear.

Is there a known fix for this?

Debian unstable — LXDE and LXQt


Topic: Polkit error — GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed  (Read 20579 times)

0 Members and 1 Guest are viewing this topic.

Offline

*

I have multiple servers and I have updated 2 of them, now I have the same error on both everytime I tried to restart any service.

I get the following error:

Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Error registering authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject (polkit-error-quark, 0)

Why we get this error? And what is the solution?


Logged


this is not any error ots some issue with new version of centos 7.8 you can disable secure processes to suppress this message.


Logged


Offline

*

this is not any error ots some issue with new version of centos 7.8 you can disable secure processes to suppress this message.

How can I disable secure processes?

And why this is not an error? This cause that some processes cannot restart and if they stop we are unable to start it, I think the system should not work like that.


Logged



Logged


Offline

*

Do not «disable secure processes» fix the real reason, Solution, test on 2 updated CentOS 7 with CWP
https://access.redhat.com/solutions/1543343

Resolution:

    Ensure the existence of a polkitd system user & group
    Copy/paste the following 2 compound-commands to a root terminal to check for and conditionally create the user/group

getent group polkitd >/dev/null && echo -e "e[1;32mpolkitd group already existse[0m" || { groupadd -r polkitd && echo -e "e[1;33mAdded missing polkitd groupe[0m" || echo -e "e[1;31mAdding polkitd group FAILEDe[0m"; }
    getent passwd polkitd >/dev/null && echo -e "e[1;32mpolkitd user already existse[0m" || { useradd -r -g polkitd -d / -s /sbin/nologin -c "User for polkitd" polkitd && echo -e "e[1;33mAdded missing polkitd usere[0m" || echo -e "e[1;31mAdding polkitd user FAILEDe[0m"; }

    Reset the permissions and user/group ownership for all files provided by the polkit and polkit-pkla-compat packages
    Copy/paste the following compound-command to a root terminal to check for and conditionally reset user/group perms & ownership

rpm -Va polkit* && echo -e "e[1;32mpolkit* rpm verification passede[0m" || { echo -e "e[1;33mResetting polkit* rpm user/group ownership & permse[0m"; rpm --setugids polkit polkit-pkla-compat; rpm --setperms polkit polkit-pkla-compat; }
    Reboot
    A reboot of the machine will be required to make sure that all changes take affect and that polkit has reconnected to the dbus

shutdown -r now


Logged


I hereby declare @NFT the winner!  ;D

A simpler method (mount modification) was posted a while back that appears to have cleared the warning. As to whether it is/was effective, is another matter.

« Last Edit: July 15, 2020, 08:28:13 AM by cynique »


Logged


Offline

*

Also tnx to the @NFT,
solved also by my side.


Logged


Offline

*

Also tnx to the @NFT,
solved also by my side.

Just notice,
temporally solved.

Problem still exists, yesterday I noticed the same message for crond :(.

Is there any solution?! It seems that there is existing problem with CentOS 7.6, even on 7.8.
It doesn�t look promising that the RedHat team will address this any time soon.


Logged


Offline

*

On centos 7, there are instances where you get the error Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Error registering authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject (polkit-error-quark, 0)

This usually happens when trying to restart a systemd service.

The workaround is as follows:

groupadd -g 23 nohidproc
usermod -a -G nohidproc polkitd
mount -o remount,rw,hidepid=2,gid=nohidproc /proc
systemctl restart polkit

Add the following in /etc/fstab as well

echo "proc /proc proc defaults,hidepid=2,gid=nohidproc 0 0" >> /etc/fstab
After mount the new mountpoint

mount -a

systemctl restart polkit
Done.

How to fix: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed Centos 7


Logged


Offline

*

I can confirm @daniellopesjp solution just worked for me.

Now I can run sh /scripts/update_cwp without these two warnings:

Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Error registering authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject (polkit-error-quark, 0)

Thanks!


Logged


I can validate this fix also. Thanks!


Logged


Понравилась статья? Поделить с друзьями:

Читайте также:

  • Xfce policykit agent error void
  • Xf86closeconsole kdsetmode failed input output error
  • Xerox ошибка немедленной перезаписи работы xerox
  • Xerox ошибка ксерографической системы xerox
  • Xerox ошибка 093 933

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии