kcookiejar on Mac OS X
Tags:
None
Registered Member 
|
As mentioned elsewhere, I'm having issues with kcookiejar functionality on OS X. There are times when it appears to work just fine, and then all of a sudden (after an upgrade to one of the KDE components?) it no longer works. This is one of those times: when I launch konqueror and then open the settings dialog, I get a message that the cookie handler service cannot be started. Sure enough, it is then impossible to log in to a gmail account, for instance.
I wonder if this is also the reason why the Akonadi google calendar resource blocks at 100% while synchronising my calendars. The google contacts resource seems to work just fine, though. This is the output I get from konqueror with all debug options selected in kdebugdialog, from the moment I request the settings dialog up to the appearance of the "cannot be started" alert:
|
Administrator
|
In this case we need to observe the output of a different process - kded4. Could you try quitting it (qdbus org.kde.kded /MainApplication quit) and launching it directly from a terminal so we can observe it's output?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
I'd already replaced kded4 by a shell wrapper that tees all output to a logfile in ${TMPDIR}/kde-${USER}/kded4.out
 Thing is, it isn't launched apparently, and your qdbus command tells me
That same (or a similar) message appears in the output I posted above. Yet I do have a /opt/local/share/dbus-1/interfaces/org.kde.kded.xml file that contains "<interface name="org.kde.kded">". I guess that a missing kded4 process will give similar effects as a dysfunctional one. I'll try logging off and back in (and rebooting if necessary) ASAP. |
|
Administrator
|
Yes, that could also cause it.
Does /opt/local/bin/kded4 exist?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Yes. It's a symlink to the kded4 wrapper script inside the OS X style application bundle, but that shouldn't make a difference.
|
|
Administrator
|
If you run "kded4" does it start successfully?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Yes, depending how you define the term
 . I no longer see errors about too many open files, but I cannot guarantee it doesn't just sit there without ever doing anything...
|
|
Administrator
|
Is it reachable over D-Bus (ie. using the previously given qdbus command)? If so, it should be able to work.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Yes, the qdbus command causes it to quit successfully.
Now the nice thing is that after yesterday's kdelibs update (in MacPorts), launching kded4 by hand will allow access to the kcookiejar:
but kded4 still doesn't get launched through the intended launchctl scripts, apparently. Maybe that a logoff/login will arrange that, will report back on that. |
|
Administrator
|
Do programs launched via launchctl get access to the session?
Usually it should be possible for kded4 to be launched automatically.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Up to this point, kded4 is the only application I noticed failing to load through the launchd scripts MacPorts put in place. Even after a re-login (actually, a reboot), so there was nothing wrong with the session dynamic data or however one calls it.
This may be something I'd need to raise on the MacPorts mailing list. |
|
Administrator
|
Is it possible to get a log from when launchd fails to start kded4?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
I've already posted logs of when kded4 fails to get started. I'm not sure launchd is the culprit (I didn't see anything suggesting that), it seems more that the current KDE-related launchd scripts are missing the required functionality.
Here's what Ian Wadham replied to my query on the MacPorts ML:
|
|
Administrator
|
The output i'm seeing above is from Konqueror and qdbus. I was hoping as launchd had specifically tried to launch kded4, it would have some logs of it's own available.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
The way I interpret things is that the failure is with qdbus or whatever is responsible for the message about a org.kde.kded service.
|
It is also partly responsible for KDE apps notBookmarks
Who is online
Registered users: bartoloni, Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]
