Reputation
780
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
6 17
Newest
 Organizer
Impact
~87k people reached

Jan
16
revised Minimal Bash-like line editing
added basic formatting
Jan
16
revised sudo apt-get update is not working in ubuntu 14.04 LTS
added basic formatting
Jan
16
awarded  Organizer
Jan
16
suggested approved edit on Minimal Bash-like line editing
Jan
16
comment How best to systematically Ubuntu Terminal language?
I’m sorry but at least to me it’s totally unclear what you are asking. It seems that your question is actually missing parts that you are referring to later? Please consider adding more details to the question which describe your actual problem.
Jan
16
comment Cannot install Ubuntu 14.04 on VirtualBox
@AlexVerzea: Have you verified the md5sum of the ISO? Even when downloading from the official website, the ISO may have become corrupted during the download.
Jan
16
suggested approved edit on sudo apt-get update is not working in ubuntu 14.04 LTS
Jan
16
reviewed No Action Needed Cleaned trash, systems files deleted
Jan
16
reviewed No Action Needed firefox: some tool boxes with black background (unreadable)
Jan
16
reviewed No Action Needed Ubuntu 14.04 32bit OS with 4g physical ram and pae still shows 3.2g ram
Jan
16
reviewed No Action Needed How to mount an Android Jelly Bean phone if there's no option?
Jan
10
revised trying to install vlc
added formatting for the terminal output
Jan
10
reviewed Reviewed trying to install vlc
Jan
10
suggested approved edit on trying to install vlc
Jan
10
reviewed Reviewed Why is X11 a security risk in servers?
Jan
10
comment udev rule seems not working properly to force the usb device into fix location
Wait, we should clarify our expectations here: the only expectation we should have is that /dev/mywebcam points to your webcam and /dev/myframegrabber points to your framegrabber. It does’t matter what /dev/video1 and /dev/video0 point to! The whole purpose of the new rules is to become independent of the latter two device node names and to instead only use the new symlinks. I have updated my answer to what seems to be the solution for your device IDs. Could you please check if your applications can use /dev/mywebcam for the webcam and /dev/myframegrabber for the framegrabber?
Jan
10
revised udev rule seems not working properly to force the usb device into fix location
updated answer according to answer discussion
Jan
9
comment udev rule seems not working properly to force the usb device into fix location
Do I understand you correctly that you have a symlink /dev/myframegrabber now which points to /dev/video1? Are you sure that ATTRS{idVendor}=="5555", ATTRS{idProduct}=="3500" really reference your framegrabber? What happens if you switch SYMLINK+="myframegrabber" and SYMLINK+="mywebcam" in the two rules?
Jan
9
revised Problem Installing podofobrowser
add link to PoDoFoBrowser so that it’s clearer what the question is about
Jan
9
comment udev rule seems not working properly to force the usb device into fix location
A symlink always has these permissions; it’s the permissions of the link target that matters. Interestingly, your symlink points to /dev/snd/controlC2 which doesn’t seem to be a video device! Are you sure that your idVendor and idProduct values are correct? Perhaps the issue is also that the device is internally treated as different devices (both audio and video capturing), not sure. If the latter should be the case, then maybe adding KERNEL=="video*" to your rules might help (but this is only a wild guess of mine).