Bug 1471952

Summary: [abrt] gvfs-mtp: run(): gvfsd-mtp killed by signal 11
Product: [Fedora] Fedora Reporter: João Carlos Mendes Luís <redhat>
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: alexl, dxzlabs, fedeb1995, hp, mzar720, oholy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ff99381bfa92401901ea574786e58313b06cd247
Whiteboard: abrt_hash:0e69d348d935487587cfcce4a87c8276bc22a52e;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 12:10:06 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: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description João Carlos Mendes Luís 2017-07-17 18:58:03 UTC
Description of problem:
Not sure.  Probably some cable failure triggered this software error.

Version-Release number of selected component:
gvfs-mtp-1.32.1-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/2
crash_function: run
executable:     /usr/libexec/gvfsd-mtp
journald_cursor: s=bb514c64aa3042f6a9a2722e5c13e5b9;i=8330ef;b=feea20a6ab584e2f95e2fc71bfe934d4;m=3b205ddbc1;t=55487ca1d671d;x=b47032feefe8776e
kernel:         4.11.9-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            40024

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 run at gvfsjobqueryinfo.c:121
 #1 g_vfs_job_run at gvfsjob.c:197
 #3 g_thread_proxy at gthread.c:784

Potential duplicate: bug 1380229

Comment 1 João Carlos Mendes Luís 2017-07-17 18:58:09 UTC
Created attachment 1300042 [details]
File: backtrace

Comment 2 João Carlos Mendes Luís 2017-07-17 18:58:10 UTC
Created attachment 1300043 [details]
File: cgroup

Comment 3 João Carlos Mendes Luís 2017-07-17 18:58:12 UTC
Created attachment 1300044 [details]
File: core_backtrace

Comment 4 João Carlos Mendes Luís 2017-07-17 18:58:14 UTC
Created attachment 1300045 [details]
File: cpuinfo

Comment 5 João Carlos Mendes Luís 2017-07-17 18:58:16 UTC
Created attachment 1300046 [details]
File: dso_list

Comment 6 João Carlos Mendes Luís 2017-07-17 18:58:17 UTC
Created attachment 1300047 [details]
File: environ

Comment 7 João Carlos Mendes Luís 2017-07-17 18:58:19 UTC
Created attachment 1300048 [details]
File: exploitable

Comment 8 João Carlos Mendes Luís 2017-07-17 18:58:20 UTC
Created attachment 1300049 [details]
File: limits

Comment 9 João Carlos Mendes Luís 2017-07-17 18:58:22 UTC
Created attachment 1300050 [details]
File: maps

Comment 10 João Carlos Mendes Luís 2017-07-17 18:58:23 UTC
Created attachment 1300051 [details]
File: open_fds

Comment 11 João Carlos Mendes Luís 2017-07-17 18:58:25 UTC
Created attachment 1300052 [details]
File: proc_pid_status

Comment 12 João Carlos Mendes Luís 2017-07-17 18:58:27 UTC
Created attachment 1300053 [details]
File: var_log_messages

Comment 13 Hein-Pieter van Braam 2017-07-26 11:24:16 UTC
Similar problem has been detected:

This happened when I unplugged a MTP device

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-mtp --spawner :1.18 /org/gtk/gvfs/exec_spaw/330
crash_function: run
executable:     /usr/libexec/gvfsd-mtp
journald_cursor: s=8a9e7701acfb4fcfbd314863a9a955a4;i=ffe80;b=9b3cf68b91e94b43ba4d5c99948a4263;m=f9804a6b7f;t=555369b66f2cd;x=750b0c783f96fe78
kernel:         4.11.9-300.fc26.x86_64
package:        gvfs-mtp-1.32.1-2.fc26
reason:         gvfsd-mtp killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Fedora End Of Life 2018-05-03 08:45:33 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 15 Fedora End Of Life 2018-05-29 12:10:06 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.