Bug 100368

Summary:	regression: kpilot daemon is not recognised although running
Product:	[Applications] kontact	Reporter:	S. Burmeister <sven.burmeister>
Component:	summary	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description S. Burmeister 2005-02-27 13:56:51 UTC

Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

kpilot daemon is started at the beginning of the session, kontact too.
However, summary in kontact states: KPilot is curently not running.
Clicking Start Kpilot does not trigger any change.

Comment 1 S. Burmeister 2005-02-27 14:02:37 UTC

Sorry, this should have been assigned to kontact!

Comment 2 Dylan Griffiths 2005-04-04 22:52:40 UTC

Confirmed in KDE 3.4.0 on Slamd64 with GCC 3.4.3/64-bit.  Starting Kontact (such that Kontact starts Kpilot) works.  However, subsequent runs of Kontact fails to show that Kpilot is running.

One interesting aspect of this bug is that there seem to be 3 formats of Kpilot data in the Kontact summary:
1) Not running.  It has 1 line which says Kpilot is not running, and gives a link to start it.
2) Running.  Kontact has last sync, user, device, status, and conduits all correctly displayed and ready to go.
3) Not running, this bug.  Like case 2, it has last sync, user, device, etc, listed.  However, last sync is "no information available."  User and device are unknown.  Conduits are none available, etc.  At the end is the case 1 "Kpilot is not running, [Start kpilot]" text.

I'm guessing it's a matter of some incorrect flow logic in the code.

Comment 3 Will Stephenson 2006-10-28 22:18:47 UTC

Confirmed, KDE 3.5.5

Comment 4 Dario Andres 2010-02-27 20:59:39 UTC

- Is this bug still valid now that KPilot went unmaintained ? Regards

Comment 5 Christophe Marin 2010-06-07 11:54:55 UTC

KPilot is now unmaintained. Changing this bug status.