Bug 1590933 - [abrt] gvfs-afc: service_receive_with_timeout(): gvfsd-afc killed by SIGSEGV
Summary: [abrt] gvfs-afc: service_receive_with_timeout(): gvfsd-afc killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ondrej Holy
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:0cfb9d7f775348df6bc69980f09...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-13 16:47 UTC by contact+rhelbugzilla
Modified: 2019-05-28 20:38 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 20:38:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.92 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: cgroup (217 bytes, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: core_backtrace (14.87 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: cpuinfo (1.40 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: dso_list (3.74 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: environ (2.61 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: exploitable (82 bytes, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: limits (1.29 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: maps (17.93 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: mountinfo (4.44 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: open_fds (510 bytes, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details
File: proc_pid_status (1.31 KB, text/plain)
2018-06-13 16:47 UTC, contact+rhelbugzilla
no flags Details

Description contact+rhelbugzilla 2018-06-13 16:47:00 UTC
Version-Release number of selected component:
gvfs-afc-1.36.2-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-afc --spawner :1.19 /org/gtk/gvfs/exec_spaw/9
crash_function: service_receive_with_timeout
executable:     /usr/libexec/gvfsd-afc
journald_cursor: s=b18f91fdd43c49f08423847048ed9a7c;i=644f2;b=50e256e6cefb455f868a3d2c995ca320;m=1b3a84e5b;t=56e88ae8b73ed;x=ceb8e265b7b2ce1c
kernel:         4.16.14-300.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 service_receive_with_timeout at service.c:157
 #1 internal_plist_receive_timeout at property_list_service.c:189
 #2 property_list_service_receive_plist_with_timeout at property_list_service.c:254
 #3 instproxy_receive_status_loop at installation_proxy.c:335
 #4 instproxy_receive_status_loop_with_callback at installation_proxy.c:488
 #5 instproxy_perform_command at installation_proxy.c:525
 #6 instproxy_browse at installation_proxy.c:585
 #7 g_vfs_backend_load_apps at gvfsbackendafc.c:1929
 #8 g_vfs_backend_afc_query_info at gvfsbackendafc.c:2170
 #9 g_vfs_job_run at gvfsjob.c:197

Comment 1 contact+rhelbugzilla 2018-06-13 16:47:03 UTC
Created attachment 1450975 [details]
File: backtrace

Comment 2 contact+rhelbugzilla 2018-06-13 16:47:04 UTC
Created attachment 1450976 [details]
File: cgroup

Comment 3 contact+rhelbugzilla 2018-06-13 16:47:05 UTC
Created attachment 1450977 [details]
File: core_backtrace

Comment 4 contact+rhelbugzilla 2018-06-13 16:47:06 UTC
Created attachment 1450978 [details]
File: cpuinfo

Comment 5 contact+rhelbugzilla 2018-06-13 16:47:07 UTC
Created attachment 1450979 [details]
File: dso_list

Comment 6 contact+rhelbugzilla 2018-06-13 16:47:08 UTC
Created attachment 1450980 [details]
File: environ

Comment 7 contact+rhelbugzilla 2018-06-13 16:47:08 UTC
Created attachment 1450981 [details]
File: exploitable

Comment 8 contact+rhelbugzilla 2018-06-13 16:47:09 UTC
Created attachment 1450982 [details]
File: limits

Comment 9 contact+rhelbugzilla 2018-06-13 16:47:10 UTC
Created attachment 1450983 [details]
File: maps

Comment 10 contact+rhelbugzilla 2018-06-13 16:47:11 UTC
Created attachment 1450984 [details]
File: mountinfo

Comment 11 contact+rhelbugzilla 2018-06-13 16:47:12 UTC
Created attachment 1450985 [details]
File: open_fds

Comment 12 contact+rhelbugzilla 2018-06-13 16:47:13 UTC
Created attachment 1450986 [details]
File: proc_pid_status

Comment 13 Ben Cotton 2019-05-02 21:35:23 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Ben Cotton 2019-05-28 20:38:36 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.


Note You need to log in before you can comment on or make changes to this bug.