Bug 5031

Created attachment 1805 [details]
lspci

The result give any indication on the webcam.
Yves

Please install the package usbutils, and then include the output
of /usr/sbin/lsusb.

CC: (none) => davidwhodgins

Here the result of lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 13d3:5111 IMC Networks Integrated Webcam

According to http://en.gentoo-wiki.com/wiki/Asus_Eee_PC_1201NL#Camera
the IMC camera should be handled by the uvcvideo kernel module.

Can you also attach /var/log/dmesg while booted from the latest kernel,
and again, after booting from the 3.2.9 kernel.

Created attachment 1811 [details]
Dmesg, for kernel 3.2.9

Created attachment 1812 [details]
Demesg for kernel 3.3

It seems that in the two cases, the module uvcvideo is loaded.
Yves

Yes, clearly the kernel module is loading in both cases.  Trying
to narrow down what the problem is.  Can you post the output of
ll /dev/vid*
getfacl /dev/vid*
from both kernels.

For kernel 3.3
ll /dev/vid*
crw-rw----+ 1 root video 81, 0 mars  21 19:40 /dev/video0

getfacl /dev/vid*
getfacl : suppression du premier « / » des noms de chemins absolus
# file: dev/video0
# owner: root
# group: video
user::rw-
user:toto:rw-
group::rw-
mask::rw-
other::---

For kernel 3.2.9-0.rt16.1.mga2

[root@eeepc toto]# ll /dev/vid*
crw-rw----+ 1 root video 81, 0 mars  21 23:23 /dev/video0
[root@eeepc toto]# getfacl /dev/vid*
getfacl : suppression du premier « / » des noms de chemins absolus
# file: dev/video0
# owner: root
# group: video
user::rw-
user:toto:rw-
group::rw-
mask::rw-
other::---

The user is not in the group video, but when added, the problem stays the same.

Correction : the eeepc is model 1005PE

For kernel 3.3
ll /dev/vid*
crw-rw----+ 1 root video 81, 0 mars  21 19:40 /dev/video0

getfacl /dev/vid*
getfacl : suppression du premier « / » des noms de chemins absolus
# file: dev/video0
# owner: root
# group: video
user::rw-
user:toto:rw-
group::rw-
mask::rw-
other::---

For kernel 3.2.9-0.rt16.1.mga2

[root@eeepc toto]# ll /dev/vid*
crw-rw----+ 1 root video 81, 0 mars  21 23:23 /dev/video0
[root@eeepc toto]# getfacl /dev/vid*
getfacl : suppression du premier « / » des noms de chemins absolus
# file: dev/video0
# owner: root
# group: video
user::rw-
user:toto:rw-
group::rw-
mask::rw-
other::---

The user is not in the group video, but when added, the problem stays the same.

Correction : the eeepc is model 1005PE

Created attachment 1849 [details]
dmseg file to use kernel-server-3.3.0-2

I have the same problem that papoteur with my laptop Acer Travelmate 7513 WSMi and the integrate webcam, it doesn't works with mageia 2 but works fine with mageia 1.

I use Mageia release 2 (Cauldron) for x86_64 Kernel 3.3.0-server-2.mga2 on a Dual-processor x86_64 / \l

In mcc ->>  Browse and configure hardware ->> Hardware ->> Unknown/others ->> USB2.0 Camera for Mageia 2 beta 2 :

Identification
Vendor: â

Description: âUSB2.0 Camera

Connection
Bus: âusb

Vendor ID: â0x5986

Device ID: â0x0100

Misc
Module: âkbd


-------------------------------------------------------------------------
-------------------------------------------------------------------------
While in mcc ->> Browse and configure hardware ->> Hardware ->> Webcam ->> USB2.0 Camera for Mageia 1: 

Identification
Vendor: âAcer, Inc

Description: âUSB2.0 Camera

Media class: âVideo|Video Control

Connection
Bus: âUSB

Bus PCI #: â1

PCI device #: â4

Vendor ID: â0x5986

Device ID: â0x0100

Misc
Module: âuvcvideo

--------------------------------------------------------
--------------------------------------------------------

The output of :

# ll /dev/vid*
crw-rw----+ 1 root video 81, 0 mars  25 22:49 /dev/video0

# getfacl /dev/vid*
getfacl : suppression du premier « / » des noms de chemins absolus
# file: dev/video0
# owner: root
# group: video
user::rw-
user:david:rw-
group::rw-
mask::rw-
other::---

# /usr/sbin/lsusb
-bash: /usr/sbin/lsusb: Aucun fichier ou dossier de ce type

----------------------------------------------------------------

It seems to be a problem with the module : âuvcvideo

I agree that it's a problem with the uvcvideo module.  Just trying to find
some useful info to help with the debugging.

As /dev/video0 is being created and the asl permissions are giving the
user read/write access to the device, what actually happens when the
program tries to access it?

Does "cheese -v" (in a terminal) provide anything other then the program
version?

So really strange, yesterday the webcam did not work with skype and neither with cheese  and nor with  amsn . And today it works with skype and cheese but not always with amsn.


For me /dev/video0 has been created 

$ cheese -v
cheese 3.3.92

$ cheese

(cheese:7803): Gtk-WARNING **: Theme directory 22x22status of theme oxygencolors(v2.4) has no size field


(cheese:7803): Gtk-WARNING **: Theme directory 32x32status of theme oxygencolors(v2.4) has no size field


(cheese:7803): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel

(cheese:7803): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel

(cheese:7803): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel

(cheese:7803): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkLabel

(cheese:7803): Gtk-WARNING **: Attempting to add a widget with type GtkGrid to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel

(cheese:7803): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkLabel

--------------------------------------------------------------------
$ rpm -qa | grep amsn
amsn-0.98.4-9.mga2

$ LC_ALL=C amsn
Unable to open mixer /dev/mixer

CC: (none) => geiger.david68210

cheese -v return only the version number.
With the two kernels, the module is kbd.
Yves

(In reply to comment #13)
> cheese -v return only the version number.
> With the two kernels, the module is kbd.

Please run
strace -f -ostrace.txt cheese

Then attach strace.txt to this bug report.

Actually, never mind.  I've now found that my webcam is also affected,
so I'll attach my strace output.

My webcam is a logitech quickcam messenger. When connected, the
following modules are loaded.

Module                  Size  Used by
snd_usb_audio          94599  1 
snd_hwdep              13274  1 snd_usb_audio
snd_usbmidi_lib        24200  1 snd_usb_audio
gspca_stv06xx          32287  0 
gspca_main             27725  1 gspca_stv06xx
videodev               70993  1 gspca_main

I'll attach strace output from both Magea 1 where it works,
and from Cauldron, where it cheese displays the message
(on the termial) ...

** (cheese:6751): WARNING **: Could not negotiate format

Created attachment 1866 [details]
strace output from Mageia 1, where camera works

Created attachment 1867 [details]
strace output from Cauldron where camera doesn't work

Created attachment 1873 [details]
strace output from Cauldron where camera doesn't work file

Created attachment 1874 [details]
strace output from Mageia 1, where camera works file

Created attachment 1878 [details]
stace with kernel 3.3 and cheese

Do you need the same with the other kernel? Or with another application like vlc?

Bug squad, please assign this bug to the kernel maintainer.

duplicate of bug 3821 maybe ?

I've attached the info about my camera to bug 3821, but will let Colin
decide if this is a duplicate bug.

Ok, there's something new for me, since the update kernel 3.3.1-1 today
my integrated webcam is recognized and  using the correct module:

Now in mcc ->> Browse and configure hardware ->> Hardware ->> Webcam ->>
USB2.0 Camera : 

Identification
Vendor: âAcer, Inc
Description: âUSB2.0 Camera
Media class: âVideo|Video Control
Connection
Bus: âUSB
Bus PCI #: â2
PCI device #: â4
Vendor ID: â0x5986
Device ID: â0x0100
Misc
Module: âuvcvideo

For le saussois,
I confirm that the module is yet uvcvideo.
But it still problems while trying to run cheese or guvcview.

For le saussois.
With the system uptodate after the RC, therre still problems:
When Cheese opens, it still grayed.
guvcview doesn't start
vlc start the blue lighting but the system freezes.

On my system, cheese still fails with "Could not negotiate format", however
xawtv -nodga -noxv-video -c /dev/video0
does work, so for my webcam, this is strictly a cheese problem.

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

After a new fresh install for Mageia 2 with the Mageia-2-x86_64-DVD, I
can confirm that the bug is resolved for me.

My integrated Webcam is now recognized with the good Module "uvcvideo".

closing then, feel free to reopen if not

Keywords: NEEDINFO => (none)
Status: NEW => RESOLVED
Resolution: (none) => FIXED

The problem is still valid for Le saussois in Mageia 2

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Hello,

I don't know if this bug is still affecting you guys on mageia 3, but today I had a problem with a logitech webcam I have that did not work with skype and amsn but it does work with Kopete.

I found a nice article here to modify a skype file and make it work with v4l1 as well as v4l2.

http://community.linuxmint.com/tutorial/view/219

The article recommends modifying /usr/local/bin/skype and adding.

#!/bin/bash
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so /usr/bin/skype


In mageia 3 would be /usr/bin/skype

Mageia already has a similar line

#!/bin/bash
LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so /usr/share/skype/skype

So I just added the next one leaving the two of them as:

#!/bin/bash
LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so /usr/share/skype/skype
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so /usr/share/skype/skype


So now all of my webcams work just fine. I just need to check amsn, but to be honest I won't use it a lot so I don't care much since skype 4 works great with my hotmail account.

Regards,

CC: (none) => ezequiel_partida

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: REOPENED => RESOLVED
Resolution: (none) => OLD