( Solved ) GDbus.Error?

[Neal ManBear]

Odd. I have yet to encounter this.      

After fixing the error message popup on login, I dug a little further.

[root@AMD64 ~]# rpm -e polkit-gnome
error: Failed dependencies:
   polkit-agent is needed by (installed) GConf2-2.32.2-1pclos2011.i586
[root@AMD64 ~]#

     
       

[djohnston]

Odd. I have yet to encounter this.      

After fixing the error message popup on login, I dug a little further.

[root@AMD64 ~]# rpm -e polkit-gnome
error: Failed dependencies:
   polkit-agent is needed by (installed) GConf2-2.32.2-1pclos2011.i586
[root@AMD64 ~]#

     
       

Neal, I guess what I was trying to say is that gconf2 is installed with Openbox WM and one of its dependencies is Gnome policy kit. I'll bet you're running LXDE 64bit. Here's what's odd. The error message that pops up on the 32bit LXDE desktop does not on the 64bit. By all accounts, it should, as shown below.



As you can see here, both Gnome's policy kit and LXDE's are tagged to run at startup. This is what happened on the 32bit installation. Unchecking Gnome's fixed the popup error. What I've yet to figure out is why it doesn't happen on the 64bit installation.

[Texstar]

Do you think the difference might be related to Gnome 3 for PCLinuxOS 64 and Gnome 2 for PCLinuxOS 32?

[Aleph]

When using bleachbit, you have to set it to save your preferred language. Edit > Preferences > Languages tab.

Hi Neal,

Thanks.

[Neal ManBear]

Neal, I guess what I was trying to say is that gconf2 is installed with Openbox WM and one of its dependencies is Gnome policy kit. I'll bet you're running LXDE 64bit. Here's what's odd. The error message that pops up on the 32bit LXDE desktop does not on the 64bit. By all accounts, it should, as shown below.

     
I saw the error for the first time this AM. Yes, it was on 32bit. And it occurred on login to root. (was checking something)     

As you can see here, both Gnome's policy kit and LXDE's are tagged to run at startup. This is what happened on the 32bit installation. Unchecking Gnome's fixed the popup error. What I've yet to figure out is why it doesn't happen on the 64bit installation.

     
Perhaps it is as Tex says.     

[djohnston]

Do you think the difference might be related to Gnome 3 for PCLinuxOS 64 and Gnome 2 for PCLinuxOS 32?

I really don't know. GConf2 (3.2.3-1), libgnome2, lib64gnome2_0 and libgnomeui2 packages are installed. The polkit-gnome version, (0.102-1), is the same version number for 32bit and 64bit. The lib64polkit-gnome0 is obviously different. The main GNOME3 packages seem to be gnome-desktop3, gnome-session-bin and gnome-settings-daemon.

The GConf2 version for 32bit is (2.32.2-1).

[Neal ManBear]

Look in /home/<your-username>/.config/autostart for the file polkit-gnome-authentication-agent-1.desktop. Delete this file! The gnome-policy-kit will not try to start up on login after.     

[Texstar]

Do you think the difference might be related to Gnome 3 for PCLinuxOS 64 and Gnome 2 for PCLinuxOS 32?

I really don't know. GConf2 (3.2.3-1), libgnome2, lib64gnome2_0 and libgnomeui2 packages are installed. The polkit-gnome version, (0.102-1), is the same version number for 32bit and 64bit. The lib64polkit-gnome0 is obviously different. The main GNOME3 packages seem to be gnome-desktop3, gnome-session-bin and gnome-settings-daemon.

The GConf2 version for 32bit is (2.32.2-1).

The reason it isn't showing up in 64bit is the polkit-gnome-authentication-agent-1.desktop executable line is pointing to the wrong location to start this service. Doesn't matter now as I will remove it from the lxde-common package.

[melodie]

Look in /home/<your-username>/.config/autostart for the file polkit-gnome-authentication-agent-1.desktop. Delete this file! The gnome-policy-kit will not try to start up on login after.    

This file exists in /usr/share/lxde/polkit : and it is recreated in the home of the user at each new session : I did a series of tests in Virtualbox last night,  and this morning, after turzin told me about the error message yesterday and asked me to test his last version with an update just after install. (He wanted to be sure he didn't mess something while tweaking things). Among other tests I tried to remove this file, reloaded the session, it was here again.

I suggested the simple solution here, deduced from the page at redhat bugzilla, as Texstar and Neal have already seen:
The new lxpolkit package generates an error at login in Lxde (Solution found). If you just leave the lxpolkit.conf do it's job and add the line:

NotShownIn=LXDE;

right at the end of the file /usr/share/lxde/polkit/polkit-gnome-authentication-agent-1.desktop, /home/user/.config/autostart/polkit-gnome-authentication-agent-1.desktop, same under /root, and in /etc/skel, it should solve it for all : the problem has been solved in my Lxde in Vbox. (Rebooted twice since, and the message didn't appear again).

Doesn't matter now as I will remove it from the lxde-common package.

That's the info I was looking for, Thanks !

Happy End of Year !

Mélodie

PS: I wonder if you could rather setup lxpolkit to be a dependency of lxde-common rather than being a dependency of pcmanfm ? How will the system react if someone wants to use pcmanfm in another desktop than Openbox or Lxde ?

[LKJ]

Look in /home/<your-username>/.config/autostart for the file polkit-gnome-authentication-agent-1.desktop. Delete this file! The gnome-policy-kit will not try to start up on login after.     

not to be argumentative but the file with the -1 is in /usr/lib the one without the -1 is in /home/.../.cong/autostart. deleting them works as does unchecking it in session startup.

[djohnston]

More than one way to skin a cat. Whoops! Sorry, Texstar. 

[Neal ManBear]

I wonder if you could rather setup lxpolkit to be a dependency of lxde-common rather than being a dependency of pcmanfm ? How will the system react if someone wants to use pcmanfm in another desktop than Openbox or Lxde ?

     
I thought you had read what Texstar said. He is updating lxde-common.      

[melodie]

I wonder if you could rather setup lxpolkit to be a dependency of lxde-common rather than being a dependency of pcmanfm ? How will the system react if someone wants to use pcmanfm in another desktop than Openbox or Lxde ?

   
I thought you had read what Texstar said. He is updating lxde-common.    

Yes Neal, you read me well. I sayd I have seen what Texstar has written : he is going to update lxde-common, and if I understood correctly he intends to remove gnome-polkit from i lxde-common, which will solve the problem. What I was saying is related to : pcmanfm which has now lxpolkit as a dependency : file manager/authentication agent... couldn't pcmanfm be free from depends else than the ones listed upstream  ? (desktop-file-utils, gtk2, libfm and lxmenu-data).

Else, if someone removes pcmanfm (and lxpolkit along with it) for his LXDE desktop system, for instance to use another file manager, what then will ensure the authentication ? :|

[Neal ManBear]

PCManFM is at the heart of LXDE and should not be removed, melodie. Too many things/functions depend on it. If you want to install and use another file manager, you can. If you're talking about remastering PCLinuxOS-LXDE with removing PCManFM, do not do that, or if you do, you will need to call it by another name.     

[melodie]

PCManFM is at the heart of LXDE and should not be removed, melodie. Too many things/functions depend on it. If you want to install and use another file manager, you can. If you're talking about remastering PCLinuxOS-LXDE with removing PCManFM, do not do that, or if you do, you will need to call it by another name.     

This is neither what I said nor what I was suggesting. I said, if someone does... which is a bit different. Also, think about it : the Lxde suite is supposed to provide most components as individual parts which can be used in other contexts than Lxde itself. Imho, this can lead to think that when a program is originally light, it would be a good thing to avoid adding depends which are not strictly required. Another example, suppose I want to make for myself a super light KDE, with the minimum KDE packages required, and I want to add PCManFM (because I like PCManFM ! Or because I am very much used to it... whatever reason). I am almost sure there is already an authentication system in KDE desktop (I don't know KDE very much... so I can only suppose, for now). What behavior will the desktop have if there is lxpolkit, brought by PCManFM, additionnally to an authentication agent already there ? Probably also error messages ? To end with, the question I wonder : couldn't lxpolkit be just linked to lxde-common and that would be it ?

Happy New Year ! It's very much paste midnight here !