Summary: | Can not start kpilot when daemon is running | ||
---|---|---|---|
Product: | [Applications] kpilot | Reporter: | Tom Albers <toma> |
Component: | General | Assignee: | groot |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | vR |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Tom Albers
2004-11-06 00:06:55 UTC
This came up on the mailing list recently and Adriaan commented with this: --------------------- You will also notice that the daemon's GUI (the tray icon) is unresponsive when using net:any and that DCOP communication with it fails. This is because it's waiting on a socket somewhere deep inside pilot-link, and I've never bothered tracking it down. I suspect that, failing pilot-link patches, the only fix is to move the pilot-communications part of the daemon to a thread, which will be pretty complicated. --------------------- It sounds like this problem will be fixed in pilot-link 0.12, so there's hope that soon this will be resolved, though not directly in kpilot. Thanks for the update! Let me know if you need a beta tester for this part. Hi Tom!! This should be fixed now. The not-yet-released version of kpilot from /branches/KDE/3.5/kdepim/kpilot should resolve this problem. Please test with that version (kpilot 4.9.1) and re-open this if you still have this problem. Thanks!! =:) |