hi aaron,
Am Mittwoch, 22. Oktober 2014, 09:59:22 schrieb Aaron Batty:
> I also had a chance to check on a student's Mac on Friday. It has only ever
> had one installation of RKWard. The behavior was there as well, so it's not
> linked to multiple installs.
ok, so we can rule that one out.
for the record, i don't see these errors on the mac i build the packages on: i
called "tail -f /private/var/log/system.log" and launched RKWard. every 10
seconds, i get a bunch of messages in endless loop, but they are not related
to dbus but OSXvnc-server/VineServer.
here some observations i made during the last round of builds -- after its
installation, the dbus port states:
# Startup items have been generated that will aid in
# starting dbus with launchd. They are disabled
# by default. Execute the following commands to start them,
# and to cause them to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-
system.plist
# launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist
in our bundle both is done, the system bus is launched by the postinstall
script, the session bus by the application itself. after the RKWard build, i
was told this:
Don't forget that dbus needs to be started as the local user (not with sudo)
before any KDE programs will launch.
To start it run the following command:
launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist
from this we can assume that the session bus is not to be started as root, so
the instructions on https://community.kde.org/Mac are outdated (and we're
doing it right).
now, this is a portion from "man launchctl":
Note that per-user configuration files (LaunchAgents) must be owned by the
user loading them. All system-wide daemons (LaunchDaemons) must be owned by
root. Configuration files must not be group- or world-writable.
hm, the way i understand this, the file "org.freedesktop.dbus-system.plist"
must then be owned by root, and the file "org.freedesktop.dbus-session.plist"
must be owned by "the user loading them". on the build mac it's:
-rw-r--r-- 1 root wheel 459 20 Okt 10:25
/opt/rkward/Library/LaunchDaemons/org.freedesktop.dbus-system.plist
-rw-r--r-- 1 root wheel 734 20 Okt 10:25
/opt/rkward/Library/LaunchAgents/org.freedesktop.dbus-session.plist
i.e., both files are owned by root and group "wheel". my user is not a member
of that group, so judging from the man page this shouldn't even work, should
it? on the other hand, i find it hard to believe that a system-wide config
file is supposed to be owned by one ordinary user and all other users can't
launch it. can you make sense of this? after all, wrong permissions could be
the actual problem here.
one other possibility might be ~/Library/Preferences/KDE. according to
https://community.kde.org/Mac it must be owned by the user, allthough i was
under the impression that this is automatically the case when it is
constructed by the first app. however, it might be interesting to have a look
on the affected systems , e.g. "ls -ld ~/Library/Preferences/KDE":
drwxr-xr-x 6 meik staff204 29 Nov 2011 KDE
what do you see? does "sudo chown -R $USER ~/Library/Preferences/KDE" make the
messages go away?
viele grüße :: m.eik
--
dipl. psych. meik michalke
institut f"ur experimentelle psychologie
abt. f"ur diagnostik und differentielle psychologie
heinrich-heine-universit"at d-40204 d"usseldorf
signature.asc
Description: This is a digitally signed message part.
--
___
RKWard-devel mailing list
RKWard-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rkward-devel
