Hi, Am Mittwoch, den 21.01.2009, 04:00 -0500 schrieb Stefan Monnier: > >> I did "apt-get update; apt-get upgrade" and now openmoko-panel-plugin > >> doesn't want to start any more. > >> > >> First I got an access error. Based on some vague googling, I replaced > >> user="root" with group="staff" in /etc/dbus-1/system.d/frameworkd.conf, > >> and it seemed to help, but not enough. Now I get an error about the > >> odeviced name being unknown (see traceback below). > >> > >> Any idea what I need to do? > > > try starting frameworkd from the command line, after stopping it > > via /etc/init.d/fso-frameworkd stop, and see if it outputs any errors. > > Hmm.. so it looks like with group="staff" frameworkd fails (presumably > because it's running as root which is not in group staff) and with > user="root", openmoko-panel-plugin fails because it's not running > as root. > > I really believe that running all apps as root is wrong. So what should > I put in /etc/dbus-1/system.d/frameworkd.conf so that both frameworkd > can start as root and openmoko-panel-plugin can run as "monnier"?
There are two quite different things configured there: Who can act as
the frameworkd daemon, and how can talk to the frameworkd daemon.
Instead of
<policy user="root">
<allow own="org.freesmartphone.opreferencesd"/>
<allow send_path="/org/freesmartphone/Preferences"/>
<allow send_destination="org.freesmartphone.Preferences"/>
<allow receive_sender="org.freesmartphone.Preferences"/>
</policy>
you should be able to write
<policy user="root">
<allow own="org.freesmartphone.opreferencesd"/>
<allow send_path="/org/freesmartphone/Preferences"/>
<allow send_destination="org.freesmartphone.Preferences"/>
<allow receive_sender="org.freesmartphone.Preferences"/>
</policy>
<policy user="monnier">
<allow send_path="/org/freesmartphone/Preferences"/>
<allow send_destination="org.freesmartphone.Preferences"/>
<allow receive_sender="org.freesmartphone.Preferences"/>
</policy>
Note that frameworkd talks to itself, so root still needs the send
rights.
So try this (duplicated for each service), and tell us your results!
Note that
--- /etc/dbus-1/system.conf_dpkg.orig 2009-01-11 00:41:57.000000000
+0100
+++ /etc/dbus-1/system.conf 2009-01-12 14:23:04.000000000 +0100
@@ -57,6 +57,7 @@
<allow send_type="signal"/>
<!-- allow sending valid replies -->
<allow send_requested_reply="true" send_type="method_return"/>
+ <allow send_requested_reply="true" send_type="method_call"/>
<allow send_requested_reply="true" send_type="error"/>
<!-- allow receiving valid replies -->
<allow receive_requested_reply="true"/>
basically disables dbus rights management, which might be ok on a
smartphone, but is not The Right Thing™ to do.
Greetings,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
