Bug 181176

Summary: cam doesnt connect, but works, also the actions are missing
Product: [Unmaintained] kopete Reporter: Wesley Velroij <velroij>
Component: WLM PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde.org, lamarque, StormByte, sune
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Wesley Velroij 2009-01-18 14:24:14 UTC
Version:           0.70.50 (using 4.2.60 (KDE 4.2.60 (KDE 4.3 >= 20090106)), Project Neon)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-3-generic

So there you are, you want to cam in Linux, to bad amsn fails, kopete detects you webcam, in the setting part, but where are the actions to invite?

Ive using Kopete since i started using KDE and I know there where always cam icons, but i can't seem to find those, and when i asked my contact to invite I didn't get any cam invite.

How to reproduce, go to settings see your cam is working, click on a contact and search for the invite cam icons, nowhere to be found.

Expected Behaviour, ofcourse that you could cam with each other.
Comment 1 Lamarque V. Souza 2009-03-21 22:57:57 UTC
I think webcam is not implemented in Kopete's WLM protocol. The MSN protocol (the same used in Kopete-3.5.x) have the "send webcam" option, but it does not seem to work. I have tried to specify a webcam port but Kopete does not save the configuration, eveytime I go there after saving the configuration the port option is disabled again.
Comment 2 Alfonso 2009-06-30 21:11:03 UTC
*** This bug has been confirmed by popular vote. ***
Comment 3 Julio Santa Cruz 2009-12-04 15:03:15 UTC
I've upgraded to Kde 4.3.2 a couple of months ago. My webcam was working seamesly in kopete before, and it works nice in the current version but only in the configuration window.
I couldn't find the option to send a webcam invitation anywhere!
Comment 4 Roman Jarosz 2010-01-17 11:02:47 UTC

*** This bug has been marked as a duplicate of bug 195228 ***