ruby 1.9 with nonblocking connection

[Subbsd]

Hello,

I'm trying to use selenium in ruby (ruby-1.9.2.290_2,1) ​​script, but
get an error like this:


/usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/common/socket_poller.rb:63:in
`connect_nonblock': Invalid argument - connect(2) (Errno::EINVAL)
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/common/socket_poller.rb:63:in
`listening?'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/common/socket_poller.rb:23:in
`block in connected?'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/common/socket_poller.rb:86:in
`with_timeout'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/common/socket_poller.rb:23:in
`connected?'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/firefox/launcher.rb:75:in
`connect_until_stable'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/firefox/launcher.rb:37:in
`block in launch'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/firefox/socket_lock.rb:20:in
`locked'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/firefox/launcher.rb:32:in
`launch'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/firefox/bridge.rb:19:in
`initialize'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/common/driver.rb:29:in
`new'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver/common/driver.rb:29:in
`for'
        from /usr/local/lib/ruby/gems/1.9/gems/selenium-webdriver-2.8.0/lib/selenium/webdriver.rb:81:in
`for'
        from test.rb:8:in `<main>'


at the 63 I see the following line on socket_poller.rb:


62          begin
63            sock.connect_nonblock sockaddr
64          rescue Errno::EINPROGRESS

any idea of ​​what could be the reason for such behavior? Thanks.