[SOLVED] authorization failure trying to access system configuration
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
authorization failure trying to access system configuration
tried to access system-->administration-->services and get a message box that says
Quote:
The configuration could not be loaded
You are not allowed to access the system configuration.
This did work; now it does not. This also fails if I switch to a console (ctl-alt f6), log in as root and switch back to desktop (ctl-alt-f7)
BACKGROUND:
I did have a problem about a month ago; I tried to add a user using
system-->administration-->users and groups; this failed and replaced the "real" /etc/group file with an empty one except for one noname entry I got that fixed using the /etc/group that was stored in /home/.Trash-0
Does anyone have any Idea how I can get back authorization to the system configuration?
(This was on my Debian-lenny system)
Last edited by garyg007; 12-19-2009 at 08:51 PM.
Reason: added info
Uhm, you are using Gnome? What services are you trying to access? What happens if you do directly to a terminal, su and type the command of the administrative task you want to perform?
I was hoping you would say something like "I did usermod -aG syslog,admin garyg (as root), then completely logged myself out and back in again and ...."
No messages other than what I referred to in my first post;
Unfortunately, it never dawned on me to check the console log (i'm not even sure where it is in debian linux)
The power supply in my debian pc failed (with healthy stink) so it will be a few days until I can get it fixed and can provide the requested cut-n-paste
Your groups are still in a mess: gary should not be a member of the groups root sudo or nogroup root should not be a member of nogroup (but it probably doesn't matter) root should be a member of just one group: root
I am surprised your system is running at all.
You'll probably have to boot from a live CD, mount your linux partition and edit /etc/group to fix it up, then unmount your linux partition, and reboot
Thanks for the info; Made the changes indicated, but I still cannot access
The system configuration; neither as user nor as root
here is another cut-n-past
Code:
Debian:/home/gary# groups gary
nogroup sys adm lp dialout fax cdrom floppy tape audio dip video plugdev users usb scanner netdev lpadmin powerdev gary fuse vboxusers admin syslog
Debian:/home/gary#
It still shows me as a member of "nogroup" -- but /etc/group DOES NOT
Hmmmmm ???
Gary
possible I edited /etc/group wrong; It was edited using command from root terminal:"gedit /etc/group"
It still shows me as a member of "nogroup" -- but /etc/group DOES NOT
Maybe something is badly broken.
Editing /etc/group by hand without a backup is probably a bad idea, using the groups and newgrp commands is a better idea, because those group numbers in /etc/group are what really matter, and it's easy to mistype a number.
You could do a clean install to a spare partition, and take a copy of the new /etc/groups file
Back in your first post you said
Quote:
I got that fixed using the /etc/group that was stored in /home/.Trash-0
How did that ( group end up in /home/.Trash-0 ) happen? Only root should be allowed to delete /etc/group, and if root deleted it, it would just be deleted, not moved to /home/.Trash-0
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.