Bug 56014 - Can't transfert File between with Empathy or Jitsi
Summary: Can't transfert File between with Empathy or Jitsi
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-15 21:32 UTC by vulcain
Modified: 2019-12-03 19:58 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Between empathy (385.12 KB, text/plain)
2012-10-15 21:32 UTC, vulcain
Details

Description vulcain 2012-10-15 21:32:33 UTC
Created attachment 68593 [details]
Between empathy

Cant' transfer file between empathy <-> empathy, empathy <-> Jisti

System: Ubuntu 12.04
Empathy 3.4.1
telepathy-gabble 0.16.0-0ubuntu2

step

1) Select acontact and with right clic go to send file
2) see a windows wich said that it wait an action of your contact
3) wait
4) wait
5) stop because it take so time

Expected: can send a file


Send Jitsi-> empathy.log 2.1 MB
http://ubuntuone.com/6FGXzVwCNlMXtPKrGWCC70

Send Emapthy->Jitsi.log 2.1 MB
http://ubuntuone.com/2xKEOyz0PtmgrUWrSKQqVQ
Comment 2 Nicolas Dufresne 2012-10-15 22:01:33 UTC
From the log, I see that SOCKS5 Bytestream endup being negotiated. But near the end of the negotiation, Jitsi returns a CANCEL(501) error marked with feature-not-implemented. Shall we mark not our bug, or is there someone that see more stuff ?
Comment 3 GitLab Migration User 2019-12-03 19:58:05 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/245.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.