Summary: | app-admin/gnome-system-tools is still not working for me | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fred Krogh <fkrogh> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | My /etc/dbus-1/system.d/org.freedesktop.SystemToolsBackends.conf |
Description
Fred Krogh
2010-01-22 01:22:05 UTC
Please list the groups your user is belonging to. Also, system-tools-backends has to be started in default runlevel. First, system-tools-backends is started at the default run level. My user is "m"; here are the groups that m belongs to. sys:x:3:root,bin,adm,m adm:x:4:root,adm,daemon,m disk:x:6:root,adm,haldaemon,m wheel:x:10:root,m floppy:x:11:root,m,haldaemon audio:x:18:m,pulse cdrom:x:19:m,haldaemon video:x:27:root,m games:x:35:m usb:x:85:root,m,haldaemon users:x:100:games,m portage:x:250:portage,m plugdev:x:409:root,m,haldaemon power:x:414:m stb-admin:x:1002:root,m malc:x:447:root,m,apache netdev:x:1000:root,m wireshark:x:1003:m pulse-access:x:1005:m Thanks for looking. also did you restart/reload dbus since you installed these packages ? (In reply to comment #3) > also did you restart/reload dbus since you installed these packages ? > Not only that, I did a complete reboot. hum, it really looks like s-t-b is not started. Could you install d-feet and check that system-tools-backends interfaces appear on the system bus ? (In reply to comment #5) > hum, it really looks like s-t-b is not started. Could you install d-feet and > check that system-tools-backends interfaces appear on the system bus ? > I'm not familiar with this tool, but after installing and running d-feet, System Bus has a line org.fsreedesktop.SystemToolsBackends system-tools-backends I think this is what you thought might not be there. Many thanks. I don't think dbus policy works that way; I don't think you can just give access to org.freedesktop.SystemToolsBackends and get it for all the sub nodes. I think the default stb-admin policy needs to include org.freedesktop.SystemToolsBackends.Platform and so on for it to work. Fred: in /etc/dbus-1/system.d/org.freedesktop.SystemToolsBackends.conf, could you copy all the lines from right above the stb-admin policy into the stb-admin policy? So, add these lines: <allow send_destination="org.freedesktop.SystemToolsBackends.Platform"/> <allow send_destination="org.freedesktop.SystemToolsBackends.GroupsConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.HostsConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.IfacesConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.NFSConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.NTPConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.ServicesConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.SMBConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.TimeConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.UserConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.UsersConfig"/> Then restart the system dbus (likely a reboot is the easiest way to do this) and let us know if it works? Thanks, but it gives the same error message as before. Just to be sure, this is what the end of /etc/dbus-1/system.d/org.freedesktop.SystemToolsBackends.conf looks like. <policy group="stb-admin"> <!-- be able to speak to the dispatcher --> <allow send_destination="org.freedesktop.SystemToolsBackends"/> <allow send_destination="org.freedesktop.SystemToolsBackends.Platform"/> <allow send_destination="org.freedesktop.SystemToolsBackends.GroupsConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.HostsConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.IfacesConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.NFSConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.NTPConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.ServicesConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.SMBConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.TimeConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.UserConfig"/> <allow send_destination="org.freedesktop.SystemToolsBackends.UsersConfig"/> </policy> </busconfig> The line just under the comment was there to begin with, the rest added as suggested. I don't know if it matters, but when I run d-feet and look at system-tools-backends under Introspection Data, there is something called Object Paths, and nothing else. ConsoleKit and Hal both have other stuff listed under Object Paths. just attach the complete file, it'll be easier to check. Created attachment 217748 [details]
My /etc/dbus-1/system.d/org.freedesktop.SystemToolsBackends.conf
The file requested
This works after: chmod a+x /usr/libexec/dbus-daemon-launch-helper I hope this is not opening up something that should not be. strange, my dbus has the exact same permission you showed and it works just fine. Perhaps I wasn't clear. Initially "ls -l /usr/libexec/dbus-daemon-launch-helper" gave "-rws--x--- 1 root messagebus 47328 Jan 21 17:23 /usr/libexec/dbus-daemon-launch-helper*". I just added root and my user to the messagebus group, and now it works with the initial permissions. |