You are not logged in.
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
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
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
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
you need to log out and log in for group changes to take effect, try that.
Offline
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
Offline
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 passwordWhile 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
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
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. Anyone who knows why this happened?
Offline
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.
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
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
Doesn't help me. Using gksudo doesn't help.
Offline
Doesn't help me. Using gksudo doesn't help.
what doesn't? what did u try to do exactly?
Offline
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
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
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
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
How to run this code? Anyone to explain?
You paste it in a terminal
Offline
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
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
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
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
Disregard this.
Last edited by sharpie (2009-09-07 02:20:34)
Offline
gpasswd -a <username> dbus
No restart necessary. Try that, it works for me.
Offline