Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 216098 - dev-ruby/xmpp4r-0.3.2 is still broken.
Summary: dev-ruby/xmpp4r-0.3.2 is still broken.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-03 22:20 UTC by Damon
Modified: 2008-11-30 16:14 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Damon 2008-04-03 22:20:52 UTC 
I seem to still be having a similar problem to bug #197606. It doesn't appear as any data is coming back from the TCP socket.

04:21:59 TLSv1: OpenSSL handshake in progress
04:22:19 TLSv1: restarting parser
04:22:19 SENDING:
    <stream:stream xmlns:stream='http://etherx.jabber.org/streams'
xmlns='jabber:client' to='gmail.com' xml:lang='en' version='1.0' >
04:22:19 EXCEPTION:
    NoMethodError
    undefined method `[]' for nil:NilClass
    /usr/lib64/ruby/1.8/rexml/source.rb:150:in `initialize'
    /usr/lib64/ruby/1.8/rexml/source.rb:16:in `new'
    /usr/lib64/ruby/1.8/rexml/source.rb:16:in `create_from'
    /usr/lib64/ruby/1.8/rexml/parsers/baseparser.rb:130:in `stream='
    /usr/lib64/ruby/1.8/rexml/parsers/baseparser.rb:107:in `initialize'
    /usr/lib64/ruby/1.8/rexml/parsers/sax2parser.rb:11:in `new'
    /usr/lib64/ruby/1.8/rexml/parsers/sax2parser.rb:11:in `initialize'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/streamparser.rb:40:in
`new'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/streamparser.rb:40:in
`parse'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:75:in
`start'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:72:in
`initialize'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:72:in `new'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:72:in
`start'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/connection.rb:102:in
`start'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:86:in
`start'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/connection.rb:156:in
`starttls'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/connection.rb:92:in
`accept_features'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/connection.rb:63:in
`connect'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:71:in
`connect'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:58:in
`connect'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:56:in
`each'
    /usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:56:in
`connect'
    twitter_test.rb:19
Exception caught in Parser thread! (NoMethodError)
/usr/lib64/ruby/1.8/rexml/source.rb:150:in `initialize'
/usr/lib64/ruby/1.8/rexml/source.rb:16:in `new'
/usr/lib64/ruby/1.8/rexml/source.rb:16:in `create_from'
/usr/lib64/ruby/1.8/rexml/parsers/baseparser.rb:130:in `stream='
/usr/lib64/ruby/1.8/rexml/parsers/baseparser.rb:107:in `initialize'
/usr/lib64/ruby/1.8/rexml/parsers/sax2parser.rb:11:in `new'
/usr/lib64/ruby/1.8/rexml/parsers/sax2parser.rb:11:in `initialize'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/streamparser.rb:40:in
`new'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/streamparser.rb:40:in
`parse'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:75:in `start'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:72:in
`initialize'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:72:in `new'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:72:in `start'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/connection.rb:102:in
`start'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:86:in `start'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/connection.rb:156:in
`starttls'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/connection.rb:92:in
`accept_features'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/connection.rb:63:in
`connect'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:71:in `connect'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:58:in `connect'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:56:in `each'
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:56:in `connect'
twitter_test.rb:19
04:22:19 STARTTLS:
    Failure: stopping only thread
        note: use sleep to stop forever
04:22:19 SENDING:
    <iq type='set' id='1302' xmlns='jabber:client'><query
xmlns='jabber:iq:auth'><username>*removed*</username><digest>*removed*</digest><resource>Testing</resource></query></iq>
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/semaphore.rb:24:in
`wait': Interrupt
        from
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/semaphore.rb:24:in `wait'
        from
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/semaphore.rb:23:in
`synchronize'
        from
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/semaphore.rb:23:in `wait'
        from
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:284:in `wait'
        from
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:349:in `send'
        from
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/stream.rb:379:in
`send_with_id'
        from
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:184:in
`auth_nonsasl'
        from
/usr/lib64/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:113:in `auth'
        from twitter_test.rb:20
Comment 1 Hans de Graaff gentoo-dev Security 2008-04-06 15:12:39 UTC 
Unfortuntnately this is the latest version that upstream released. Judging from the error this is a problem in the upstream code, so it is probably best to report this upstream (although they don't seem to have a bug tracker).
Comment 2 Hans de Graaff gentoo-dev Security 2008-11-30 16:14:57 UTC 
I've just added xmpp4r-0.4 to CVS, which may fix the problems you are seeing.