Bug 176100 - webcam start when kopete start
Summary: webcam start when kopete start
Status: RESOLVED NOT A BUG
Alias: None
Product: kopete
Classification: Applications
Component: Audio/Video Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-26 00:25 UTC by Marc Collin
Modified: 2010-07-04 14:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Collin 2008-11-26 00:25:22 UTC 
Version:           0.60.3 (using 4.1.3 (KDE 4.1.3) "release 55.1", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.25.18-0.2-default

when i use a Logitech QuickCam Communicate STX and i start kopete, my led webcam become blue... in the kopete webcam option... i see nothing

i use gspca driver

this webcam work fine with skype, motion and camstream
Comment 1 Lamarque V. Souza 2009-03-21 22:51:42 UTC 
Maybe this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=167332
Comment 2 Frank Schaefer 2010-03-06 16:49:59 UTC 
Ok Marc, let's see if we can fix it:

1.) What does "I see nothing" mean ?
Is the device detected / shown in the device combobox ?
What do you see exactly in the preview area ? Does it show the webcam icon or is it black or green ?

2.) What is the USB-ID of this device ?

3.) openSUSE 11.0 shipped kernel 2.6.25. The GSPCA-driver has been reworked and improved very much for kernel 2.6.27. Could you please try again with a newer kernel (openSUSE 11.1 or 11.2) ?

4.) Only if you are using KDE < 4.4.1:
Make sure libv4l is installed on your system and start Kopete with

LD_PRELOAD=/usr/lib/libv4/v4l2convert.so kopete

Does that make the device work ?
Comment 3 Frank Schaefer 2010-05-24 16:23:23 UTC 
Ping !? Any news for us ?
Comment 4 Frank Schaefer 2010-07-04 14:51:49 UTC 
No reply since ~4 months and the provided bug description/information is completely insufficient.

So I have to close this bug as invalid.