You are not logged in.

#1 2008-01-26 07:49:43

B-Con
Member
From: USA
Registered: 2007-12-17
Posts: 554
Website

You are not allowed to access the system configuration.

Whenever I try to run one of the programs from the gnome-system-tools package (with gksu or gksudo) I get an error:

The configuration could not be loaded

You are not allowed to access the system configuration.

From the console, I get:

(time-admin:8036): Liboobs-WARNING **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files

(time-admin:8036): Liboobs-WARNING **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files

This seems to be similar to a persistent bug in Ubuntu. Everything in the thread and bug report linked to from the thread seem to revolve around needing to use gksudo, ensuring there exists an admin group, things I've already checked and/or don't apply.

Last edited by B-Con (2008-01-26 08:03:02)

Offline

#2 2008-01-27 09:38:18

Moo-Crumpus
Member
From: Hessen / Germany
Registered: 2003-12-01
Posts: 1,487

Re: You are not allowed to access the system configuration.

Your user needs to be member of the group stb-admin, and you need to start the daemon stbd.

gpasswd -a <username> stb-admin
/etc/rc.d/stbd start

Last edited by Moo-Crumpus (2008-01-27 11:21:32)


Frumpus addict
[mu'.krum.pus], [frum.pus]

Offline

#3 2008-01-27 13:16:12

fettouhi
Member
Registered: 2007-05-07
Posts: 745

Re: You are not allowed to access the system configuration.

Moo-Crumpus wrote:

Your user needs to be member of the group stb-admin, and you need to start the daemon stbd.

gpasswd -a <username> stb-admin
/etc/rc.d/stbd start

I have the same problem but I already added my user to stb-admin and stbd is running in the background and I still can't access the system configuration.

Regards

André

Offline

#4 2008-01-27 17:18:44

bender02
Member
From: UK
Registered: 2007-02-04
Posts: 1,328

Re: You are not allowed to access the system configuration.

Well, does 'su' work for you guys on the command line? (I think you need to be in the group 'wheel' for that.) And does 'sudo'?

Sorry if it's offtopic, I really don't know much about gnome.

Offline

#5 2008-01-27 20:26:38

sinister99
Member
Registered: 2007-04-10
Posts: 136

Re: You are not allowed to access the system configuration.

you need to log out and log in for group changes to take effect, try that.

Offline

#6 2008-01-27 22:46:13

rocknrolf77
Member
From: Oslo, Norway
Registered: 2007-05-07
Posts: 68

Re: You are not allowed to access the system configuration.

Have the same problem here. I'm a member of both groups and have done everything here. But still get the same message. My  time is totally wrong. It's really annoying sad

Offline

#7 2008-01-28 00:01:45

B-Con
Member
From: USA
Registered: 2007-12-17
Posts: 554
Website

Re: You are not allowed to access the system configuration.

Moo-Crumpus wrote:

Your user needs to be member of the group stb-admin, and you need to start the daemon stbd.

gpasswd -a <username> stb-admin
/etc/rc.d/stbd start

Tried it. Now I get a different error:

Failed to run users-admin as user root.

Failed to communicate with gksu-run-helper.

Received:
/bin/su: incorrect password

While expecting:
gksu: waiting

That's if I run it with gksu. However if I sudo su into root and try to run it, it actually runs but fails to populate the user and group lists.

Also, I'm somewhat bothered that *root* is not recognized as having permission to execute something. Why would root ever be denied permission to execute whatsoever it pleases?


@rocknrolf: Lookup date -s . Not the pretty GUI way to do it, but it does the job.

Last edited by B-Con (2008-01-28 00:16:14)

Offline

#8 2008-01-28 02:16:03

jacko
Member
Registered: 2007-11-23
Posts: 840

Re: You are not allowed to access the system configuration.

My  time is totally wrong. It's really annoying sad

ntpd ntpdate solved it for me. Check the ntp wiki entry.

Last edited by jacko (2008-01-28 02:18:12)

Offline

#9 2008-01-31 19:19:58

rocknrolf77
Member
From: Oslo, Norway
Registered: 2007-05-07
Posts: 68

Re: You are not allowed to access the system configuration.

Nothing is helping. Still got the no rights problem. Giving the password with gksu time-admin and I get the no rights message. root user in terminal gives the same message too.

Something strange happened. Booted XP and changed to the right time. Then I got the right time in arch after reboot.  hmm Anyone who knows why this happened?

Offline

#10 2008-01-31 20:03:15

B-Con
Member
From: USA
Registered: 2007-12-17
Posts: 554
Website

Re: You are not allowed to access the system configuration.

rocknrolf77 wrote:

Nothing is helping. Still got the no rights problem. Giving the password with gksu time-admin and I get the no rights message. root user in terminal gives the same message too.

Same here.

B-Con wrote:

Also, I'm somewhat bothered that *root* is not recognized as having permission to execute something. Why would root ever be denied permission to execute whatsoever it pleases?

I'm still bothered by this, *root* is being denied permission. What subtle nuances are going on here, and is there a way around them? Is this some sort of another "user-helpful" Gnome feature gone awry?

Last edited by B-Con (2008-01-31 20:03:41)

Offline

#11 2008-02-10 17:09:32

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: You are not allowed to access the system configuration.

For me, it did not work. I added myself to stdb-admin and admin groups. I would get "The configuration could not be loaded."

I looked at ubuntu, and I noticed that they gksudo prefixed in the launcher. Adding that worked. The PKGBUILD should patch the *.desktop files.

for file in `pacman -Ql gnome-system-tools | grep desktop | cut -d" " -f2`; do cat $file | sudo sed 's/\(^Exec=\)\(.*-admin\)/\1gksudo \2/g' | sudo tee temp.desktop.tmp; sudo mv temp.desktop.tmp $file; done

Offline

#12 2008-02-10 22:07:21

B-Con
Member
From: USA
Registered: 2007-12-17
Posts: 554
Website

Re: You are not allowed to access the system configuration.

Doesn't help me. Using gksudo doesn't help.

Offline

#13 2008-02-11 16:39:20

jacko
Member
Registered: 2007-11-23
Posts: 840

Re: You are not allowed to access the system configuration.

B-Con wrote:

Doesn't help me. Using gksudo doesn't help.

what doesn't? what did u try to do exactly?

Offline

#14 2008-02-11 23:09:57

B-Con
Member
From: USA
Registered: 2007-12-17
Posts: 554
Website

Re: You are not allowed to access the system configuration.

jacko wrote:
B-Con wrote:

Doesn't help me. Using gksudo doesn't help.

what doesn't? what did u try to do exactly?

$ gksudo users-admin

The configuration could not be loaded

You are not allowed to access the system configuration

Same thing since the start of the thread.

Last edited by B-Con (2008-02-11 23:10:12)

Offline

#15 2008-02-12 01:04:09

jacko
Member
Registered: 2007-11-23
Posts: 840

Re: You are not allowed to access the system configuration.

Same thing since the start of the thread

did you try this fix?

I looked at ubuntu, and I noticed that they gksudo prefixed in the launcher. Adding that worked. The PKGBUILD should patch the *.desktop files.

for file in `pacman -Ql gnome-system-tools | grep desktop | cut -d" " -f2`; do cat $file | sudo sed 's/\(^Exec=\)\(.*-admin\)/\1gksudo \2/g' | sudo tee temp.desktop.tmp; sudo mv temp.desktop.tmp $file; done

Last edited by jacko (2008-02-12 01:05:04)

Offline

#16 2008-02-12 01:28:54

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: You are not allowed to access the system configuration.

jacko wrote:

Same thing since the start of the thread

did you try this fix?

I looked at ubuntu, and I noticed that they gksudo prefixed in the launcher. Adding that worked. The PKGBUILD should patch the *.desktop files.

for file in `pacman -Ql gnome-system-tools | grep desktop | cut -d" " -f2`; do cat $file | sudo sed 's/\(^Exec=\)\(.*-admin\)/\1gksudo \2/g' | sudo tee temp.desktop.tmp; sudo mv temp.desktop.tmp $file; done

It fixed it for me.

Offline

#17 2008-02-12 02:01:53

B-Con
Member
From: USA
Registered: 2007-12-17
Posts: 554
Website

Re: You are not allowed to access the system configuration.

jacko wrote:

Same thing since the start of the thread

did you try this fix?

I looked at ubuntu, and I noticed that they gksudo prefixed in the launcher. Adding that worked. The PKGBUILD should patch the *.desktop files.

for file in `pacman -Ql gnome-system-tools | grep desktop | cut -d" " -f2`; do cat $file | sudo sed 's/\(^Exec=\)\(.*-admin\)/\1gksudo \2/g' | sudo tee temp.desktop.tmp; sudo mv temp.desktop.tmp $file; done

Nope. Still doesn't work, on both machines I tried on.

Offline

#18 2008-02-13 13:19:18

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: You are not allowed to access the system configuration.

din_vl wrote:

How to run this code? Anyone to explain? roll

You paste it in a terminal

Offline

#19 2008-02-13 13:24:30

din_vl
Member
Registered: 2008-01-30
Posts: 46

Re: You are not allowed to access the system configuration.

I got it.
I add user to stbd group, start stbd and it works without any code.

Last edited by din_vl (2008-02-13 13:34:24)

Offline

#20 2008-03-02 02:23:31

B-Con
Member
From: USA
Registered: 2007-12-17
Posts: 554
Website

Re: You are not allowed to access the system configuration.

Ah, if I add myself to stb-admin and start stbd works with gksudo.

[edit]
Grammar.

Last edited by B-Con (2009-08-18 03:49:38)

Offline

#21 2009-08-17 20:42:17

cetinsert
Member
Registered: 2009-08-17
Posts: 4

Re: You are not allowed to access the system configuration.

You may want to make sure that dbus is somewhere among the daemons started at boot time:

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(... dbus ...)

I had forgotten to put it there at install time and adding it did the trick for me!

Last edited by cetinsert (2009-08-17 20:43:06)

Offline

#22 2009-08-18 02:16:08

majiq
Member
Registered: 2009-03-06
Posts: 259

Re: You are not allowed to access the system configuration.

cetinsert wrote:

You may want to make sure that dbus is somewhere among the daemons started at boot time:

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(... dbus ...)

I had forgotten to put it there at install time and adding it did the trick for me!

.....................first off, welcome to the forums.

Secondly, and this is actually a common problem, this thread is pretty old. You may want to check dates before posting next. :-)

Offline

#23 2009-08-27 05:29:43

sharpie
Member
From: Phoenix, AZ
Registered: 2008-11-16
Posts: 72

Re: You are not allowed to access the system configuration.

Disregard this.

Last edited by sharpie (2009-09-07 02:20:34)

Offline

#24 2009-09-07 02:21:11

sharpie
Member
From: Phoenix, AZ
Registered: 2008-11-16
Posts: 72

Re: You are not allowed to access the system configuration.

gpasswd -a <username> dbus

No restart necessary.  Try that, it works for me.

Offline

Board footer

Powered by FluxBB