[jitsi-dev] [jitsi] File transfer via jit.si (#132)


#1

When I drag and drop messages in to the chat I get the following error.
The above message could not be delivered, failed to deliver.
My operating system is Ubuntu 14.04.2 LTS
My jitsi version is Jitsi 2.8.5426

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132


#2

// , Can you add some code to that, please?

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-110525259


#3

// , Tried it out myself. Got this:

![selection_003](https://cloud.githubusercontent.com/assets/5750764/8071603/a6572fa4-0ec0-11e5-98dc-9528ddb615d3.png)

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-110527770


#4

// , Sometimes it work, 'n sometimes it dn't.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-110527816


#5

// , Here's the code related to the WhenIsGood(5)-1.ics file:

    15:58:16.681 SEVERE: [232] impl.protocol.jabber.OperationSetFileTransferJabberImpl.run().660 An exception occured while transfering file:
    Error in execution:
      -- caused by: java.util.concurrent.ExecutionException: No response from file transfer initiator:
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer.negotiateStream(IncomingFileTransfer.java:199)
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer.access$100(IncomingFileTransfer.java:47)
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer$1.run(IncomingFileTransfer.java:124)
        at java.lang.Thread.run(Thread.java:745)
    Nested Exception:
    java.util.concurrent.ExecutionException: No response from file transfer initiator:
        at java.util.concurrent.FutureTask.report(FutureTask.java:122)
        at java.util.concurrent.FutureTask.get(FutureTask.java:202)
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer.negotiateStream(IncomingFileTransfer.java:193)
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer.access$100(IncomingFileTransfer.java:47)
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer$1.run(IncomingFileTransfer.java:124)
        at java.lang.Thread.run(Thread.java:745)
    Caused by: No response from file transfer initiator:
        at org.jivesoftware.smackx.filetransfer.StreamNegotiator.initiateIncomingStream(StreamNegotiator.java:97)
        at org.jivesoftware.smackx.filetransfer.IBBTransferNegotiator.createIncomingStream(IBBTransferNegotiator.java:80)
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer$2.call(IncomingFileTransfer.java:186)
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer$2.call(IncomingFileTransfer.java:183)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer.negotiateStream(IncomingFileTransfer.java:190)
        ... 3 more

The successful transfer produced no errors.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-110528063


#6

Closed #132.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#event-377004324


#7

// , Why was this closed?

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-133576836


#8

// , Pretty serious bug, if someone asked me.

···

---
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-133576883


#9

I also have this issue, when I try to send someone an amazon link on version 2.10.5550 on a Mac to a Windows host running the exact same version.

···

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-278459161


#10

// , I think most people find a way to deal with it by generic troubleshooting, but it's still a pretty ambiguous error.

···

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-279442757


#11

// , @ibauersachs, would you consider re-opening this?

···

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi/issues/132#issuecomment-279442960