Bug 651678 – Cancelling a copy operation terminates gvfsd-afc with SIGPIPE

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 651678 - Cancelling a copy operation terminates gvfsd-afc with SIGPIPE


Summary:	Cancelling a copy operation terminates gvfsd-afc with SIGPIPE


Status:	RESOLVED DUPLICATE of bug 649041

Product:	gvfs
Classification:	Core
Component:	afc backend and volume monitor
Version:	git master
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	gvfs-maint
QA Contact:	gvfs-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-06-02 01:42 UTC by Nikias Bassen
Modified:	2011-08-29 14:13 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Nikias Bassen 2011-06-02 01:42:33 UTC

If you copy a file with nautilus to your idevice and cancel the copy operation,
the mount disappears. Running gvfsd-afc with gdb showed me that a SIGPIPE is the reason for this behaviour:

[...]
Queued new job 0x692ad0 (GVfsJobWrite)
job_write send reply
Queued new job 0x692b60 (GVfsJobWrite)
job_write send reply

Program received signal SIGPIPE, Broken pipe.
0x00007ffff6fefc5d in write () at ../sysdeps/unix/syscall-template.S:82
82	../sysdeps/unix/syscall-template.S: Datei oder Verzeichnis nicht gefunden.
	in ../sysdeps/unix/syscall-template.S
(gdb) bt

+ Trace 227347

#0 write
at ../sysdeps/unix/syscall-template.S line 82
#1 ??
from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#2 g_main_context_dispatch
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 ??
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 g_main_loop_run
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 ??
#6 ??
#7 __libc_start_main
at libc-start.c line 226
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??

Comment 1 Tomas Bzatek 2011-08-29 14:13:45 UTC


*** This bug has been marked as a duplicate of bug 649041 ***