Thanks for the summary Thibaut. The permissions for ~/Library/
Preferences/KDE were ok but, to be safe, I reran the command suggested
by the compilation output. To no avail unfortunately ...
More observations: after a complete restart, I can see dbus-daemon
running in Activity Monitor, but no kuiserver. After running kile from
the symbol, I can also see kdeinit4 and "KDE Daemon", but no kile or
kuiserver. A second doubleclick on kile doesn't change anything.
When I run kuiserver from the symbol or from the command line, it
opens as an app that has as an icon an empty page with a question
mark, and the only menu item is "kuiserver". It shows up in Activity
Monitor with an empty name. No error messages whatsoever. Starting
kile afterwards doesn't succeed either.
If that gives a clue: when I issue "launchctl load -w /Library/
LaunchAgents/org.freedesktop.dbus-session.plist" right after a
restart, I get "org.freedesktop.dbus-session: Already loaded". The
similar "launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-
system.plist" goes through without complaint.
Where do I have to look for more precise information on what's going
wrong?
Cheers
Thomas
On 28 Nov 2010, at 17:41, Thibaut Cousin wrote:
Le 28 nov. 2010 à 16:18, Thomas Schneider a écrit :
I've installed kile-devel via a freshly selfupdated MacPorts 1.9.2
on Mac OS 10.6.5. Together with other KDE 4 applications it depends
on, kile now sits in
/Applications/MacPorts/KDE4/ .
When I start kile from Finder, nothing happens -- CPU usage
doesn't even increase.
When I start
/Applications/MacPorts/KDE4/kile.app/Contents/MacOS/kile
from the command line, the small "Kile 2.1 beta 4" window opens,
and I get a trace that ends in " Stopped kile.app/Contents/MacOS/
kile". That trace is attached below as Trace 1, and it doesn't
contain anything that looks explicitly like an error to me. In
addition, drkonqi is opened. It tells me:
"We are sorry, Kile closed unexpectedly. [...] Details: Executable:
kile PID: 538 Signal: 6 (Abort trap)"
I made a fresh install just last week, and I do not have this
problem, but I had to follow a couple of steps to have kile-devel
working :
1) I had to change the authorizations on ~/Library/Preferences/KDE,
as suggested by a message in the compilation output. Nothing would
start without this, even without any previous installation.
2) I had to start it twice. The first time only kuiserver started
(if I remember correctly). I quit it and relaunched Kile, and then
everything was fine.
--
Thibaut Cousin
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
--
Thomas Schneider
Pommernring 16
66121 Saarbrücken
[email protected]
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
