hey i am ahaving a little problem in
a
Debian testing distribution on a Dell laptop.
Everything used to be ok , and then maybe i changed something i should not.
Any how now , i do not have access to manage my network-admin in gnome just because when i open it the gui doesnt let me change anything i am just able to see the options. the strange thing is that when i open it it doesnt ask me for a root password anymore.

Also when i open the user and group gnome applet , i cannot do anything even for the normal user.

I beleive that all started when i did put synaptic on the keyring manager.
Another strange thing is that i am not able to change any section in the gnome menu except the 'other' sretion. Lets say if i try to add a game in the games section i try to do it , but when i finidh nothing actually happens.
Please any help

I haven't seen this myself, but sounds like something could have gone wrong with gksu - the graphical frontend for su and sudo. What happens if you open a terminal window and type, e.g.:
Do you get prompted for a password now? Can you go into the network settings applet and change things?

If this does not work, try su-ing to root, and then launch the control center. This ought to let you make changes.

If the problem started when you added Synaptic to the keyring, you could try removing it again. If this doesn't work, try re-installing gsku:

When i open the control centre i get this error:


Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)



And when openong the networ-admin i get the following on the terminal:

(network-admin:4309): CRITICAL **: Cannot create session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Any ideas on that?? i also reinstalled gksu but nothing there still no access. I think that once before i might have done something wrong, like changing the ownership and access of my /home/user/ folder

This is a guess.

You might try to boot as a single user and from there set the root password again. There are guides and advice in how this is available on line and in this forum. I do not know if this would solve the problem with su, but it might give you a way to set or reset such things as users and permissions.

Good Luck