Working on it.

CC: (none) => mageia
Assignee: bugsquad => mageia

I just imported "luvcview" on "cauldron".
WIP for "guvcview".

Status: NEW => ASSIGNED

(In reply to comment #2)
> I just imported "luvcview" on "cauldron".
> WIP for "guvcview".

@ Damien
Do you have any news?

CC: (none) => marja11

http://svnweb.mageia.org/packages?view=revision&revision=166215
guvcview is now available in Cauldron.
You can test it and close the bug if working as expected.
Thanks.

Many thanks indeed for that but as I don't have Cauldron enabled, is there a way to install it without enabling Cauldron.

Generally, for package requests that were solved for Cauldron but not yet for stable:

The package has dependencies. If the required packages and at least the required versions of those packages aren't in Mga 1, you'll need to pull them in as well. Some of those packages can depend on other packages that aren't in Mga1, so you'll need to get them from the cauldron repositories as well.. and so on.

I didn't check to see whether "1" solves all the dependencies, though, sorry, but here is the list for i586:

Requires

    rpmlib(PayloadFilesHavePrefix) <= 4.0-1
    rpmlib(CompressedFileNames) <= 3.0.4-1
    libSDL-1.2.so.0
    libavcodec.so.53
    libc.so.6
    libc.so.6(GLIBC_2.0)
    libc.so.6(GLIBC_2.1)
    libc.so.6(GLIBC_2.11)
    libc.so.6(GLIBC_2.2)
    libc.so.6(GLIBC_2.3.4)
    libc.so.6(GLIBC_2.4)
    libgdk-3.so.0
    libglib-2.0.so.0
    libgobject-2.0.so.0
    libgtk-3.so.0
    libm.so.6
    libm.so.6(GLIBC_2.0)
    libm.so.6(GLIBC_2.1)
    libpango-1.0.so.0
    libpng15.so.15
    libportaudio.so.2
    libpthread.so.0
    libpthread.so.0(GLIBC_2.0)
    libpthread.so.0(GLIBC_2.2)
    libpulse-simple.so.0
    libpulse.so.0
    librt.so.1
    librt.so.1(GLIBC_2.2)
    libudev.so.0
    libv4l2.so.0
    rtld(GNU_HASH)
    rpmlib(PayloadIsLzma) <= 4.4.6-1

Dear Marja & others,

If users of '1' are mixing stuff destined for '1' with stuff destined for 'Cauldron', then somewhere down the road it can lead to instable '1' and possibility of loosing support for '1'. I'm wondering, with all due respect, if this is the best course of action. IMHO it could only be solved properly by backporting the said packages to '1' level and enabling '1-backports'.

If one enables Cauldron repositories while trying to keep stable '1', I believe that in fact one may end up with troublesome maintenance or running true Cauldron.

YMMV, HTH

CC: (none) => dvgevers

Yes, I agree entirely because I need to install and test the guvcview package which Damien has been kind enough to package but, as things stand at the moment, I cannot do that. Yesterday, I followed the instructions on the Wiki and attempted to "upgrade" my "1" installation to Cauldron but it was a total and utter disaster. Fortunately, I cloned my "1" installation before hand so I was able to restore it after the failed attempt. This now leaves me wondering how I can install, test and report my findings without doing a Cauldron installation on a seperate partition??

I believe you have 3 options: * virtualbox (or similar), * use a separate partition, * use a friend's box.

I finally decided to do a complete Cauldron install on a fresh partition using the boot.iso and everything went perfectly. After installing guvcview, I have a problem (see next post) .....

(In reply to comment #4)
> http://svnweb.mageia.org/packages?view=revision&revision=166215
> guvcview is now available in Cauldron.
> You can test it and close the bug if working as expected.
> Thanks.

Installed it and, after clicking the guvcview icon in the Sound & Video section of the Application Launcher, I'm getting the following error message:

----------
Guvcview error:
Unable to open device.
Please make sure the camera is connected and that the correct driver is installed.
----------

The device is a Sweex WC060 HD Webcam (USB) and it's definitely plugged in.
As for the correct driver, I don't have a clue with that?

As I found out only days ago: you may have to turn it on by means of (for example) a certain key combination, depending on your hardware: in my case - a particular kind of laptop - it was Fn key plus F10 key as per written instructions that came with the laptop.

WRT a driver I may revert later (on someone else?)

Alternatively, if above doesn't help, according to http://www.ideasonboard.org/uvc/ the application luvcview should support your 'cam.

Please try: 

urpmi luvcview

It works for me.

Well, it's a funny old life isn't it:
Prior to switching off my PC yesterday afternoon, nothing had changed WRT to my previous findings. However, after booting the PC this morning, one of the first things I did was to try guvcview and guess what, it's now working and I haven't changed anything :-))

After giving guvcview a good workout, it appears to be working perfectly, so I'll mark this "bug" as RESOLVED.

Many thanks to Damien for packaging the application and to everyone else for their input and help.

Status: ASSIGNED => RESOLVED
Resolution: (none) => WORKSFORME