Bug 248584

Summary:	Error message - Cannot start process googletalk-call. Check your installation of Kopete
Product:	[Unmaintained] kopete	Reporter:	Mark Fraser <mfraz74+kde>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	andrew, ivan, leggis, mschiwi, pali.rohar
Priority:	NOR
Version First Reported In:	0.3
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Mark Fraser 2010-08-21 10:59:47 UTC

Version:           0.3 (using KDE 4.5.0) 
OS:                Linux

When I load Kopete and try to connect to Facebook via Jabber, I get the above error appear in a box. If I try again it will connect.

Reproducible: Didn't try

Steps to Reproduce:
Load up Kopete, connect to Facebook chat via Jabber. Error box appears. Close error box, connect again. Connection successful.



Kubuntu 10.10 alpha 3.
OS: Linux (i686) release 2.6.35-17-generic
Compiler: cc

Comment 1 Mark Fraser 2010-08-21 11:15:20 UTC

OK, I've fixed this by installing the package kopete-gcall.

Comment 2 Mark Fraser 2010-08-28 12:10:43 UTC

Did another update and now it is broken again, get 2 warnings every time I run Kopete.

Comment 3 Schiwi 2010-08-28 18:21:15 UTC

Same problem here

Comment 4 Mark Fraser 2010-08-28 20:17:20 UTC

Is it related to this https://bugs.launchpad.net/kopete/+bug/625088 bug?

Comment 5 Schiwi 2010-08-28 20:44:30 UTC

(In reply to comment #4)
> Is it related to this https://bugs.launchpad.net/kopete/+bug/625088 bug?

yes, seems so

Comment 6 Ivan D Vasin 2010-09-08 17:11:33 UTC

this problem appeared after i installed google-talkplugin.  it persists even after i remove that package.  as noted in comment #1, a workaround is to install google-talkplugin together with kopete-gcall.

Comment 7 Pali Rohár 2013-06-05 19:11:55 UTC

this is kubuntu specific packaging problem, so closing as invalid here.

Comment 8 Pali Rohár 2013-06-05 19:12:38 UTC

*** Bug 250566 has been marked as a duplicate of this bug. ***