Stelian, please take a look at the backtrace below... does it ring any bells?
it probably happens when a connection times out, or in some unusual situation. please not the "unconnected" part in the socket's print-object output...
some more info: after this, or something that causes this, or... slime-connect hangs while half-way connected.
-- attila