Thanks for the info. As you have found (or rather not found when netsearching!) the symptoms you report are unusual. That suggests that they are caused by something unusual about your system. It is possible that this "something unusual" is hinted at by the response given by "rpm -qi VirtualBox". Have you any ideas why it is not simply reporting "*'is not installed'*" as expected?

It might be worth doing an rpm uninstall, manually removing the files in the rpm VirtualBox package if rpm is too broken to do it automatically, then uninstalling and reinstalling by whichever system you used to install the VirtualBox PUEL version.

Hello catkin,
first of all thanx for your time and effort to help me.
Second, i checked the rpm problem. I found i have libnss3 in firefox directory so i added that to ld.so.conf and now is working. The rpm -qi VirtualBox gives "package VirtualBox is not installed" but that is not problem i dont use rpm. I am slackware user The test script from this site gives no error anymore. Here is the output:

"VirtualBox PUEL version found. OK.
Name of user used to run VirtualBox: domine
This computer has udev rules file for VirtualBox, /etc/udev/rules.d/10-vboxdrv.rules. OK.
No fstab usbfs line found. udev rules are effective.
Group name used for VirtualBox USB access is vboxusers.
Group vboxusers found in /etc/group. OK.
Here is the group line from /etc/group:
vboxusers:x:102:domine
User domine is in group vboxusers/102. OK.
Access mode used for VirtualBox USB access is 0664.
Access mode (0664) includes 'group write'. OK.
Kernel module vboxdrv loaded. OK.
All tests passed. OK. :-)"

Everything should work as expected but no. No luck. I did reinstall the whole VB and linux like two times and every time deleting the ~.VirtualBox directory. I used that version of VBOX: VirtualBox-3.0.10-54097-Linux_amd64.run. May be there is a bug in that one. The only really strange thing is that every time i use devgid the systems halts. I used 102(vboxusers),83(plugdev) and 10(wheel). No use. When i remove the devgid but leave the devmode then the slackware32 loads ok in VB but no USB. By the way i have installed the guest additions. At least i think so. How can one check? I followed the rules though. And before the guest additions installed i couldnt autoresize the window. After the autoresize was working. So i guess the additions are installed properly.

groups domine gives this:
domine : users wheel audio video plugdev vboxusers

Still any idea about the devgid problem?
Thanks for whatever comes on your mind

PS: can you post description of your configuration? to compare may be smth will come up

Hello Domine

So the script's warning was caused by a broken rpm system, now fixed -- a red herring.

A resizeable display is good indication of GuestAdditions being installed. AFAIK GuestAdditions is not required for USB functionality but I don't run without it so have not tested.

Here's output from the USB test script on Slackware 13.0 32-bit with VirtualBox installed from VirtualBox-3.0.10-54097-Linux_x86.runHere are the udev rulesIf that's all similar to your system maybe there's a clue somewhere in the ~/.VirtualBox/Machines/<machine name>/Logs files or /var/log files. When you write "the systems halts" do you mean the VM system or the whole host system?

Best

Charles

Hi catkin,
update on my story
Now i changed the fstab to:
usbfs /proc/bus/usb usbfs devgid=83,devmode=0664,busgid=83,busmode=775 0 0

where devgid is the plugdev id. Then started the VB. The mouse and keyboard are captured i think and i cant use them in host or guest. Then i wait for lilo to load and i have my Slackware32 running. Then i have keyboard and mouse in the guest(in console mode) then when i startx i dont see the mouse anymore but is still there I can open terminal and i can see the usb works Then when i shutdown -h now the guest the mouse and keyboard are coming back to host.
I saw before that such behavior is observed when devgid is 102(vboxusers) and 83(plugdev) should allow the mouse and keyboard to function normally in host and guest.
So now i have to find out how to disable autocapture in VBox without starting the virtual machine. Because if i start i dont have mouse in host even if i press right ctrl and i cant press that button on the menu bar Is there a config file where i can do that disabling to check what will be the effect.

Greetings
Domine

Hi again,
i tried and with that:
usbfs /proc/bus/usb usbfs devgid=102,devmode=0664

same story. no input in host and input in guest after its loaded fully.

i manage to get usb working adding

to fstab

this way i can use my no-name webcam )

Ok thanks for the info i will try that as well. Is it a problem to show me your:

/lib/udev/rules.d/50-udev-default.rules

I think there may be a problem here. But not sure yet. Just to compare.
Thanks

here it is http://pastebin.ca/1671004

thanx. is the same as mine
but no luck still.
so now my problem is different how to make the mouse and keyboard work in both host and guest.
interesting. i use now such fstab line:

usbfs /proc/bus/usb usbfs auto,devmode=0664,devgid=83 0 0

devgid the group of plugdev and i am in it. but still the host cant use the input.

Have you configured your mouse and keyboard in Menu->System->"Sun VirtualBox"-><machine name>->USB? If so, it would give the symptoms you report!

Hello catkin,
it works finally. yes that was the problem. i have added the mouse and keyboard(cos they are usb) to the usb as the webcam. now i unchecked that in the settings and now i have my mouse and keyboard in host and guest and usb as well
thanks a lot for the help. i dont understand only one thing. why they made it so complicated. i mean add usb rule for the webcam but not for the mouse and keyboard(when they are usb - most of the cases). its creating a mess. but now all is fine. now hopefully the skype will actually produce some video
thanks again for helping me going through that vodoo thing

cheers
Domine

solution summary:
1.add your user to groups vboxusers and plugdev
2.add to fstab:
usbfs /proc/bus/usb usbfs devmode=0664,devgid=83 0 0

devgid=83 the id of the plugdev group

3.add rule for the webcam or whatever other usb device in the settings for the virtual machine but dont add rule for usb mouse or keaboard.


SOLVED
Great success!

Hello Domine

Good news it's solved

I made the same mistake myself, when I installed VirtualBox for the first time using 1.6.0. I guess the reason is that the host needs the mouse and keyboard and the guest borrows them from the host when it has focus -- as generic mouse and keyboard, rather than as USB devices. The wonder is that more people don't make the same mistake. Sorry it took me so long to remember.

You probably don't need the fstab line; the udev rules are enough.

A similar situation can arise with CD and DVD drives if they are mounted on both host and guest.

Best

Charles

Hi Charles,
i see, i tried just of curiosity if it will work only with the udev rules. Nope its not. I need the fstab line. Anyway now is working. Even made the skype to work with v4lcompat.so Nice. Im happy. Now i can speak to my wife without rebooting to windows. I dont like that I try to stay away from windows it makes me nervous

Best
Dimitar