Bug 888997

Summary: [abrt] mtpfs-1.1-0.3.svn20120510.fc18: parse_path: Process /usr/bin/mtpfs was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Gerard Ryan <fedora>
Component: mtpfsAssignee: Orphan Owner <extras-orphan>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: extras-orphan, stebbins
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:30b6454f52c4102fede510f7d4105f626e4119bf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:03:52 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: open_fds
none
File: proc_pid_status none

Description Gerard Ryan 2012-12-20 00:22:01 UTC
Description of problem:
I was using mtpfs to copy some files to my android device. It was my first time doing this, so it might be user error.

Steps to reproduce:
1. mkdir /media/XperiaS/
2. mtpfs /media/XperiaS/
3. cd /media/XperiaS/Internal\ Storage/Music/
4. I was coping stuff to here when this abrt occured. I had selected several directories from a USB mass storage device to copy here.

I don't know how reproduceable this is, or if it's even considered a bug, since it's my first time using mtpfs

A couple of other things that I found odd (probably known):

1. Device shows up in nautilus after mounted by mtpfs. Two directories can be seen, "Internal Storage" and "Playlists". Double-clicking on "Playlists" opens the directory as expected (it is empty however - expected I think). Double-clicking to open "Internal Storage" produces strange behaviour: opens a new nautilus window of /media/XperiaS/, rather than opening /media/XperiaS/Internal Storage/ in the current window.

2. Copying a file (or files) to the device from a terminal blocks everything. I can't switch to a different terminal tab or different window, or different desktop workspace. Everything is blocked for an undetermined amount of time. I'm not sure if it's until the current file has finished copying, or something else.

Version-Release number of selected component:
mtpfs-1.1-0.3.svn20120510.fc18

Additional info:
backtrace_rating: 4
cmdline:        mtpfs /media/XperiaS/
crash_function: parse_path
executable:     /usr/bin/mtpfs
kernel:         3.6.10-5.fc18.x86_64
uid:            1000
var_log_messages: Dec 19 23:46:58 localhost abrt[30104]: Saved core dump of pid 18953 (/usr/bin/mtpfs) to /var/spool/abrt/ccpp-2012-12-19-23:46:56-18953 (107134976 bytes)

Truncated backtrace:
Thread no. 1 (7 frames)
 #6 parse_path at mtpfs.c:465
 #8 mtpfs_getattr_real at mtpfs.c:881
 #9 mtpfs_getattr at mtpfs.c:916
 #10 lookup_path at fuse.c:2466
 #11 fuse_lib_lookup at fuse.c:2665
 #12 fuse_ll_process_buf at fuse_lowlevel.c:2441
 #13 fuse_do_work at fuse_loop_mt.c:117

Potential duplicate: bug 869444

Comment 1 Gerard Ryan 2012-12-20 00:22:05 UTC
Created attachment 666449 [details]
File: backtrace

Comment 2 Gerard Ryan 2012-12-20 00:22:07 UTC
Created attachment 666450 [details]
File: cgroup

Comment 3 Gerard Ryan 2012-12-20 00:22:09 UTC
Created attachment 666451 [details]
File: core_backtrace

Comment 4 Gerard Ryan 2012-12-20 00:22:11 UTC
Created attachment 666452 [details]
File: dso_list

Comment 5 Gerard Ryan 2012-12-20 00:22:13 UTC
Created attachment 666453 [details]
File: environ

Comment 6 Gerard Ryan 2012-12-20 00:22:15 UTC
Created attachment 666454 [details]
File: limits

Comment 7 Gerard Ryan 2012-12-20 00:22:18 UTC
Created attachment 666455 [details]
File: maps

Comment 8 Gerard Ryan 2012-12-20 00:22:20 UTC
Created attachment 666456 [details]
File: open_fds

Comment 9 Gerard Ryan 2012-12-20 00:22:22 UTC
Created attachment 666457 [details]
File: proc_pid_status

Comment 10 John Stebbins 2013-03-29 00:33:48 UTC
Mount MTP device (Nook HD+) with mtpfs (e.g. mtpfs /mnt/mtp)
Attempt to copy several files
After a few files are copied, a failure occurres with the message:
cp: cannot stat ‘/mnt/mtp/XXX.epub’: Transport endpoint is not connected

dmesg shows the error:
[292048.754080] traps: mtpfs[1802] general protection ip:3d1367bdad sp:7f5624b233c0 error:0 in libc-2.16.so[3d13600000+1ad000]


backtrace_rating: 4
Package: mtpfs-1.1-0.3.svn20120510.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 11 Fedora End Of Life 2013-12-21 10:00:07 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 12 Fedora End Of Life 2014-02-05 14:03:54 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.