Bug 76432

Summary:	Starting cvsservice failed with message: KDEInit could not launch 'cvsservice'
Product:	[Unmaintained] kdelibs	Reporter:	Jeroen Wijnhout <spam>
Component:	kdeinit	Assignee:	Christian Loose <christian.loose>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jeroen Wijnhout 2004-02-29 18:01:30 UTC

Version:           unknown (using KDE 3.2.1, compiled sources)
Compiler:          gcc version 3.3.1 (SuSE Linux)
OS:          Linux (i686) release 2.4.21-192-athlon

Hi,

I usually start Cervisia as a different user:
kde -u kde-dev -c cervisia

Sometimes (seems random) I get the following message in a message box:

Starting cvsservice failed with message: KDEInit could not launch 'cvsservice'

After that I can retry start Cervisia as many times as I want to no avail. The same happens with KDevelop.

Restart KDE does help, usually.

Sorry for the vague bug report, I'd be happy to help you track down the problem, but I don't really know where to begin.

best,
Jeroen

Comment 1 Christian Loose 2004-04-02 10:25:59 UTC

Some info i gathered so I don't forget...

This is message is created in kdelibs/kinit/klauncher.cpp - KLauncher::requestDone().

call order seems to be:
-----------------------

KLauncher::start_service_by_desktop_name()
KLauncher::start_service()
KLauncher::queueRequest()
KLauncher::slotDequeue()
KLauncher::requestStart()
-- kinit.cpp --
handle_requests()
handle_launcher_requests()
launch()
-- kinit.cpp --
KLauncher::slotKDEInitData()
KLauncher::processDied()    <-- unsure
KLauncher::requestDone()    <-- probably with request->status = KLaunchRequest::Error

Comment 2 Christian Loose 2004-09-20 11:45:54 UTC

I have to admit that I'm not making any progress here. Maybe one of the kdeinit gurus have an idea what could cause this problem.

Christian

Comment 3 Waldo Bastian 2004-09-21 12:57:18 UTC

It basically means that the "cvsservice" executable was not found by kdeinit or that the cvsservice loadable module, if such thing exists, could not be loaded by kdeinit, e.g. due to missing or wrong symbols.

Comment 4 Christian Loose 2005-04-19 13:28:49 UTC

Thanks Waldo for the additional info.

Jeroen: do you still have this problem?

Comment 5 Jeroen Wijnhout 2005-04-22 11:04:07 UTC

I can't reproduce it anymore, but I haven't used Cervisia much lately either.

However, the comment from Waldo seems spot on. The problem can be reproduced by trying to start Cervisia/KDE 3.3 under KDE 3.4, probably a binary incompat. problem. At the time I reported this problem I only had one KDE version installed, but the binary packages I used then _could_ be flawed. Don't know for sure of course.

I'm ok with closing this bug report, I will reopen if I ever manage to reproduce it properly.

best,
Jeroen

Comment 6 Christian Loose 2005-04-22 11:41:35 UTC

Thanks for the reply.

Yes, we do have a binary incompatibility problem with the libcvsservice library ATM. 

The library contains the generated DCOPStub classes for the cvs DCOP service. Unfortunately the tool dcopidl2cpp declares the methods as virtual (I didn't know that) and we added new methods to the service.

So this could create problems in a mixed KDE 3.3/3.4 environment. You'll have to make sure that Cervisia finds the right version of libcvsservice and the DCOP service.

Since I don't think that has anything to do with your original problem, I'm closing this for now.