Cannot get my microsaft life 3000 webcam to for in cheese and skype.

Asked by David Franks

I have a microsoft life 3000 web cam that i cannot get to work in Cheese and Skype. I have upgraded to Ubuntu 16.04 from 14.04 and hope that it would work in the latest software. I couldn't get it to work n 14.04. I can get a picture in Cheese but no sound and in Skype nothing. I have very limited computer knowledge so would appreciate any instructions in a very simple form.
I have tried several times to load on presumably drivers but nothing happens.
I would like to find a way to get it to work especially as I'm a pensioner and cannot afford to replace it. I do need to have it operational as my daughter is leaving South Africa to live in Hong Kong and this will be, hopefully, my main means f communicating with her and the family.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
David Franks
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

What is the output of:

lsb_release -a; uname -a; lsusb

Thanks

Revision history for this message
David Franks (franksdavid3) said :
#2

Hi I'm afraid I don't know what you're asking or where to find the information. As I said I'm not just dumb when it comes to these things but proberly dumber than dumb. Having said that with the right guidance I can usually the answer. Do you want me to copy what you sent and enter it via the terminal?

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Copy the command and press CTRL + ALT + T

Paste the command into the terminal and hit ENTER

Copy the output and paste as an update on:
https://answers.launchpad.net/ubuntu/+question/295607

Revision history for this message
David Franks (franksdavid3) said :
#4

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

david@david-AMILO-Pro-Edition-V3545:~$ lsb_release -a; uname -a; lsusb
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial
Linux david-AMILO-Pro-Edition-V3545 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 1199:6802 Sierra Wireless, Inc. MC8755 Device
Bus 005 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 003 Device 002: ID 0458:00e8 KYE Systems Corp. (Mouse Systems)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
david@david-AMILO-Pro-Edition-V3545:~$

Hope this is what you asked for

Revision history for this message
David Franks (franksdavid3) said :
#5

I ran the command again with the lfe cam in & here is the report

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

david@david-AMILO-Pro-Edition-V3545:~$ To run a command as administrator (user "root"), use "sudo <command>".
bash: syntax error near unexpected token `('
david@david-AMILO-Pro-Edition-V3545:~$ See "man sudo_root" for details.
No command 'See' found, did you mean:
 Command 'pee' from package 'moreutils' (universe)
 Command 'see' from package 'mime-support' (main)
 Command 'tee' from package 'coreutils' (main)
 Command 'ree' from package 'ree' (universe)
See: command not found
david@david-AMILO-Pro-Edition-V3545:~$
david@david-AMILO-Pro-Edition-V3545:~$ david@david-AMILO-Pro-Edition-V3545:~$ lsb_release -a; uname -a; lsusb
david@david-AMILO-Pro-Edition-V3545:~$: command not found
Linux david-AMILO-Pro-Edition-V3545 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Bus 001 Device 005: ID 045e:0779 Microsoft Corp. LifeCam HD-3000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 1199:6802 Sierra Wireless, Inc. MC8755 Device
Bus 005 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 003 Device 002: ID 0458:00e8 KYE Systems Corp. (Mouse Systems)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
david@david-AMILO-Pro-Edition-V3545:~$ No LSB modules are available.
No: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Distributor ID:Ubuntu
Distributor: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Description:Ubuntu 16.04 LTS
Description:Ubuntu: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Release:16.04
Release:16.04: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Codename:xenial
Codename:xenial: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Linux david-AMILO-Pro-Edition-V3545 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Linux: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
No command 'Bus' found, did you mean:
 Command 'bus' from package 'atm-tools' (universe)
Bus: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Bus 005 Device 002: ID 1199:6802 Sierra Wireless, Inc. MC8755 Device
No command 'Bus' found, did you mean:
 Command 'bus' from package 'atm-tools' (universe)
Bus: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
No command 'Bus' found, did you mean:
 Command 'bus' from package 'atm-tools' (universe)
Bus: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
No command 'Bus' found, did you mean:
 Command 'bus' from package 'atm-tools' (universe)
Bus: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Bus 003 Device 002: ID 0458:00e8 KYE Systems Corp. (Mouse Systems)
bash: syntax error near unexpected token `('
david@david-AMILO-Pro-Edition-V3545:~$ Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
No command 'Bus' found, did you mean:
 Command 'bus' from package 'atm-tools' (universe)
Bus: command not found
david@david-AMILO-Pro-Edition-V3545:~$ Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
bash: syntax error near unexpected token `('
david@david-AMILO-Pro-Edition-V3545:~$ Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
No command 'Bus' found, did you mean:
 Command 'bus' from package 'atm-tools' (universe)
Bus: command not found
david@david-AMILO-Pro-Edition-V3545:~$ david@david-AMILO-Pro-Edition-V3545:~$
david@david-AMILO-Pro-Edition-V3545:~$: command not found
david@david-AMILO-Pro-Edition-V3545:~$

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#6

If you run:

sudo modprobe -r uvcvideo
sudo modprobe uvcvideo

Then rerun cheese, is it OK?

Revision history for this message
David Franks (franksdavid3) said :
#7

When I enter the command in the terminal it asks for my password. It doesn't let me type it in although it's the password I use normally

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#8

Your password is being accepted. You just don't get any feedback.

Revision history for this message
David Franks (franksdavid3) said :
#9

Mmmm well when I type it in I comes back and says sorry try again
You seem to have patience, well you'll need it with me lol

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#10

Your password is the one you login with. It is case sensitive.

You did set a password when you installed the OS...

Revision history for this message
David Franks (franksdavid3) said :
#11

Hi Andrew, I've set it up that when I switch on the laptop it automatically opens up so I don't use a password there. when it goes into sleep mode, and i need to get in, it asks for my password which I type in and then it opens up for me. I use the same password with the respective upper case letters in the terminal. When in the terminal and it asks for my password I get the flashing cursor but I cannot type anything there, it just remains there flashing. have already tried inputing my password but again no joy just 'sorry try again'. I cannot even type exit to get out, I need to press enter 3 times till it gets to a point where I can type exit and close the terminal.
I've also tried just pressing enter but also no joy.

Revision history for this message
David Franks (franksdavid3) said :
#12

Hope this gives you a bit more carity.

avid

Revision history for this message
David Franks (franksdavid3) said :
#13

orry that should be David

Revision history for this message
Manfred Hampl (m-hampl) said :
#14

If you get the request to enter the password for the sudo command and you start typing, you will not get any feedback (no echo, not even '*' placeholders).

Just 'blind' type your password and press the 'enter' or 'return' key.

(Remark: in a terminal window you can abort most commands by pressing ctrl-c)

Revision history for this message
David Franks (franksdavid3) said :
#15

Hi Manfred, have tried what you suggested. I did it last night and again when I got your msg. Well no go, either I'm too stupid and am doing the wrong things or the laptop is stupid and doesn't understand me lol

Revision history for this message
Manfred Hampl (m-hampl) said :
#16

Just to make sure that I do not misunderstand:

You know your password.
If you wake up your computer from sleep mode, you have to enter your password, and it is working there.
The command "sudo modprobe -r uvcvideo" requests the password, but if you enter it you get "sorry try again"

Is this correct?

If you open a terminal window and start typing you password, do you see the correct password shown (immediately delete it afterwards with the backspace character, nobody else should see it)?

Revision history for this message
David Franks (franksdavid3) said :
#17

Your understanding is correct. If I open the terminal and type my password it shows up correctly. I also tried the ctrl-c command you suggested and that also didn't work.

Revision history for this message
Manfred Hampl (m-hampl) said :
#18

ctrl-c is no command, but can abort other commands.
If you start a "sudo whatever_command" operation, and want to abort it, you can press ctrl-c, and you should be returned to the command prompt for entering a new command.

Still it is not clear for us, why your password does not work for sudo.

Try the following:

open a terminal window and issue the three commands (one after the other)

groups
id
sudo id

For the last one you will be asked for the password. Just 'blind' type it in and press enter.

When you have done all that (no matter what the results are), use the terminal window's menu entries "edit - select all" and "edit - copy", and paste everything into this question document, that we can see the results.

Revision history for this message
David Franks (franksdavid3) said :
#19

david@david-AMILO-Pro-Edition-V3545:~$ groups
david adm cdrom sudo dip plugdev lpadmin sambashare
david@david-AMILO-Pro-Edition-V3545:~$ id
uid=1000(david) gid=1000(david) groups=1000(david),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare)
david@david-AMILO-Pro-Edition-V3545:~$ sudo id
[sudo] password for david:
uid=0(root) gid=0(root) groups=0(root)
david@david-AMILO-Pro-Edition-V3545:~$ edit-select all
edit-select: command not found
david@david-AMILO-Pro-Edition-V3545:~$ edit-copy
edit-copy: command not found
david@david-AMILO-Pro-Edition-V3545:~$

I hope that I've done this correctly

Revision history for this message
Manfred Hampl (m-hampl) said :
#20

Hooray, the password worked for the "sudo id" command, and I assume you will be able to do the same also for other commands now.

("edit - select" and "edit - copy" were not meant as commands to enter, but as mouse-click on the respective menu entries. In any case that did not matter, because you were able to copy/paste the output).

Now please try the commands

sudo modprobe -r uvcvideo
sudo modprobe uvcvideo
luvcview

and copy/paste the output as done before.

Revision history for this message
David Franks (franksdavid3) said :
#21

david@david-AMILO-Pro-Edition-V3545:~$ groups
david adm cdrom sudo dip plugdev lpadmin sambashare
david@david-AMILO-Pro-Edition-V3545:~$ id
uid=1000(david) gid=1000(david) groups=1000(david),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare)
david@david-AMILO-Pro-Edition-V3545:~$ sudo id
[sudo] password for david:
uid=0(root) gid=0(root) groups=0(root)
david@david-AMILO-Pro-Edition-V3545:~$ edit-select all
edit-select: command not found
david@david-AMILO-Pro-Edition-V3545:~$ edit-copy
edit-copy: command not found
david@david-AMILO-Pro-Edition-V3545:~$ sudo modprobe -r uvcvideo
[sudo] password for david:
Sorry, try again.
[sudo] password for david:
david@david-AMILO-Pro-Edition-V3545:~$

Ok sorry misunderstood about the mouse click thing. Well am glad I go a hooray so must be some progress lol. Just don't tell me I have no hope and must go back to Microsoft Vista

Revision history for this message
Manfred Hampl (m-hampl) said :
#22

Two more commands:

sudo modprobe uvcvideo
luvcview

Revision history for this message
David Franks (franksdavid3) said :
#23

sudo: 3 incorrect password attempts
david@david-AMILO-Pro-Edition-V3545:~$
david@david-AMILO-Pro-Edition-V3545:~$ sudo modprobe uvcvideo luvcview
[sudo] password for david:
david@david-AMILO-Pro-Edition-V3545:~$ david@david-AMILO-Pro-Edition-V3545:~$ sudo modprobe uvcvideo luvcview
david@david-AMILO-Pro-Edition-V3545:~$: command not found
david@david-AMILO-Pro-Edition-V3545:~$ [sudo] password for david:
[sudo]: command not found
david@david-AMILO-Pro-Edition-V3545:~$ david@david-AMILO-Pro-Edition-V3545:~$
david@david-AMILO-Pro-Edition-V3545:~$: command not found
david@david-AMILO-Pro-Edition-V3545:~$ sudo modprobe uvcvideo luvcview
david@david-AMILO-Pro-Edition-V3545:~$ HappyDede
HappyDede: command not found
david@david-AMILO-Pro-Edition-V3545:~$ sudo modprobe uvcvideo
david@david-AMILO-Pro-Edition-V3545:~$ luvcview
No command 'luvcview' found, did you mean:
 Command 'guvcview' from package 'guvcview' (universe)
luvcview: command not found

Glad you have patience lol

Revision history for this message
Manfred Hampl (m-hampl) said :
#24

I just see that luvcview does no more exist on Ubuntu 16.04, so there is no need to try running that program.

What is the output of the command

ls -l /dev/video*

Revision history for this message
David Franks (franksdavid3) said :
#25

david@david-AMILO-Pro-Edition-V3545:~$ ls -l /dev/video*
crw-rw----+ 1 root video 81, 0 Jun 24 12:33 /dev/video0
david@david-AMILO-Pro-Edition-V3545:~$

This is all I go when I ran the command

Revision history for this message
Manfred Hampl (m-hampl) said :
#26

Your problem might be caused by access restrictions. You have to be granted membership in a specific group to get access to the camera.

Execute the following command in a terminal window.

sudo useradd -G video david

Then log out, and log in again (or restart the computer).
Finally try using the camera.

Revision history for this message
David Franks (franksdavid3) said :
#27

david@david-AMILO-Pro-Edition-V3545:~$ sudo useradd -G video david
[sudo] password for david:
useradd: user 'david' already exists

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#28

If you run:

sudo cheese

Do you see yourself OK?

Revision history for this message
David Franks (franksdavid3) said :
#29

Yep can see myself and take a pic. video works but no sound. Have check the settings that I know of. Here is the copy from the terminal.

(cheese:2002): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
david@david-AMILO-Pro-Edition-V3545:~$

I haven't tried loading Skype down yet But in 14.04 I didn't get pic or sound. the ring test didn't even work

Revision history for this message
Manfred Hampl (m-hampl) said :
#30

Since my previous command for adding your user to the video group did not work (was my fault), try again with

sudo usermod -aG video david

and then log out and log in again (or restart the computer)
afterwards re-try running cheese (without sudo), and can you see the image from the camera?

Revision history for this message
David Franks (franksdavid3) said :
#31

I can see the pic but still no sound when in video mode. I also still have the situation that hen it asks for a password i get the sorry try again. Eventually I go back to the command entry line. The Indicator flashed But as soon as I enter it sort of freezes and I can't input mu password. Have the same problem when I tried to install skype via the terminal

Revision history for this message
Manfred Hampl (m-hampl) said :
#32

Apparently the camera is already accessible.
What password prompt are you getting?
What exactly is freezing?

Revision history for this message
David Franks (franksdavid3) said :
#33

Hi Manfred the Cheese and Skype are now working perfectly. Thanks for your help and patience. The only problem that doesn't seem to be resolve is the input of my password in the terminal when it comes back and says sorry try again

Revision history for this message
Manfred Hampl (m-hampl) said :
#34

What is causing this request for a password?

Revision history for this message
David Franks (franksdavid3) said :
#35

 When I want to sometime do something via the terminal it will ask for my password. For example when i did the command you sent me (sudo modprobe -r uvcvideo). The cursor block was flashing, as soon as I pressed the cap arrow to enter my password it stopped flashing and whatever I entered for my password was not accepted and i got the sorry msg. Whilst I don't often do things thro the terminal it can give me grey hairs when i do need to d things that way

Revision history for this message
Manfred Hampl (m-hampl) said :
#36

Providing your password for sudo has worked well in some of the commands above.
I do not see a reason that it would fail on a random basis.
I suggest that you just try again if you get the 'sorry...' response, and carefully and slowly type the password to make sure that you do not mistype it.

Revision history for this message
David Franks (franksdavid3) said :
#37

Thanks will do and once again thanks for the help, it's much appreciated.