Bug 1276236

Summary: [abrt] gvfs: g_simple_async_result_set_error(): gvfs-udisks2-volume-monitor killed by SIGSEGV
Product: [Fedora] Fedora Reporter: fedbzville
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: alexl, bnocera, oholy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3ca341ef25ed1bb8b6c36eb03941e01472b5007d
Whiteboard: abrt_hash:5ff2f03177497a0a1efa7cfcfe0baadca437486b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:21:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description fedbzville 2015-10-29 08:05:31 UTC 
Description of problem:
I used Files to eject a USB key at the same time as writing to an external USB hard drive. It's the first time I have ever done this, and it's the first time I have ever seen this issue.

Version-Release number of selected component:
gvfs-1.24.2-1.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/libexec/gvfs-udisks2-volume-monitor
crash_function: g_simple_async_result_set_error
executable:     /usr/libexec/gvfs-udisks2-volume-monitor
global_pid:     2324
kernel:         4.2.3-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1002

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_simple_async_result_set_error at gsimpleasyncresult.c:719
 #1 mount_op_reply_handle at gvfsudisks2mount.c:666
 #2 unmount_show_busy at gvfsudisks2mount.c:819
 #3 unmount_cb at gvfsudisks2mount.c:869
 #4 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #5 reply_cb at gdbusproxy.c:2623
 #6 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #7 g_dbus_connection_call_done at gdbusconnection.c:5502
 #8 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #9 complete_in_idle_cb at gsimpleasyncresult.c:775
Comment 1 fedbzville 2015-10-29 08:05:36 UTC 
Created attachment 1087400 [details]
File: backtrace
Comment 2 fedbzville 2015-10-29 08:05:37 UTC 
Created attachment 1087401 [details]
File: cgroup
Comment 3 fedbzville 2015-10-29 08:05:39 UTC 
Created attachment 1087402 [details]
File: core_backtrace
Comment 4 fedbzville 2015-10-29 08:05:40 UTC 
Created attachment 1087403 [details]
File: dso_list
Comment 5 fedbzville 2015-10-29 08:05:42 UTC 
Created attachment 1087404 [details]
File: environ
Comment 6 fedbzville 2015-10-29 08:05:43 UTC 
Created attachment 1087405 [details]
File: limits
Comment 7 fedbzville 2015-10-29 08:05:45 UTC 
Created attachment 1087406 [details]
File: maps
Comment 8 fedbzville 2015-10-29 08:05:46 UTC 
Created attachment 1087407 [details]
File: mountinfo
Comment 9 fedbzville 2015-10-29 08:05:48 UTC 
Created attachment 1087408 [details]
File: namespaces
Comment 10 fedbzville 2015-10-29 08:05:49 UTC 
Created attachment 1087409 [details]
File: open_fds
Comment 11 fedbzville 2015-10-29 08:05:50 UTC 
Created attachment 1087410 [details]
File: proc_pid_status
Comment 12 fedbzville 2015-10-29 08:05:52 UTC 
Created attachment 1087411 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:21:53 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.