Bug 40861

Summary:	FileTransfer: cancel a file transfer on A is not received on B
Product:	Telepathy	Reporter:	Simon Schampijer <simon>
Component:	salut	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	0.4
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Attachments:	Logs from A the sender of the file transfer Logs from B the receiver of the file transfer

Description Simon Schampijer 2011-09-14 01:46:50 UTC

Created attachment 51180 [details]
Logs from A the sender of the file transfer

Steps to reproduce:

- open a file transfer on A for B

- on B do not accept/decline it

- cancel the file transfer on A

---> B should receive a notification that the file transfer has been canceled

Looking at the tp-salut logs (version 0.4) on A we do call 
salut-file-transfer-channel.c:salut_file_transfer_channel_do_close which does call tp_svc_channel_emit_closed (self). On B, we never receive any notification about that. 

As far as I understood from http://telepathy.freedesktop.org/spec/Channel_Type_File_Transfer.html#Signal:FileTransferStateChanged A has to only call 'Close' on the channel which we do in Sugar when a file transfer is canceled like described in the scenario from above.

Comment 1 Simon Schampijer 2011-09-14 01:47:40 UTC

Created attachment 51181 [details]
Logs from B the receiver of the file transfer

Comment 2 GitLab Migration User 2019-12-03 20:15:36 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-salut/issues/31.

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.