Description of problem: Tried to mount a Samsung Galaxy S3 android phone. mkdir ~/Samsung_Galaxy_S3 mtpfs -o allow_other ~/Samsung_Galaxy_S3 The mtpfs resulted in: Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 20 Attempting to connect device Listing File Information on Device with name: SCH-I535 and then the mtpfs process was killed with SIGABRT. Version-Release number of selected component: mtpfs-1.1-0.2.svn20120510.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: mtpfs -o allow_other /home/jrg3/Samsung_Galaxy_S3 crash_function: standard_free kernel: 3.6.1-1.fc17.i686.PAE truncated backtrace: :Thread no. 1 (10 frames) : #6 standard_free at gmem.c:98 : #8 parse_path at mtpfs.c:465 : #10 mtpfs_getattr_real at mtpfs.c:881 : #11 mtpfs_getattr at mtpfs.c:916 : #12 fuse_fs_getattr at fuse.c:1115 : #13 lookup_path at fuse.c:1854 : #14 fuse_lib_lookup at fuse.c:2047 : #15 do_lookup at fuse_lowlevel.c:518 : #16 fuse_ll_process at fuse_lowlevel.c:1525 : #17 fuse_session_process at fuse_session.c:80
Created attachment 629081 [details] File: core_backtrace
Created attachment 629082 [details] File: environ
Created attachment 629084 [details] File: backtrace
Created attachment 629085 [details] File: limits
Created attachment 629086 [details] File: cgroup
Created attachment 629087 [details] File: maps
Created attachment 629088 [details] File: dso_list
Created attachment 629089 [details] File: var_log_messages
Created attachment 629090 [details] File: open_fds
Installed mtpfs so I could communicate to Kindle Fire -- setup up mount point (/mnt/kindle) -- setup /etc/udev/rules.d/51-android.rules Attempts to mount the device failed. If mount as user then /mnt/kindle was always blank If mount as root then I could 'ls' through the file system If I tried to copy a file to the file system, received an error about missing transport end point Rebooted system ... and had the failure that auto-prompted for a bug report backtrace_rating: 4 Package: mtpfs-1.1-0.2.svn20120510.fc17 OS Release: Fedora release 17 (Beefy Miracle)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.