Bug 1325436

Summary: Cannot mount iPod with gvfs-afc
Product: [Fedora] Fedora Reporter: rosenp
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: alexl, bnocera, oholy, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-20 04:10:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
log from journalctl none

Description rosenp 2016-04-08 19:47:57 UTC
Description of problem:
I feel that this is an iFuse problem. When I mount the iPod as root to any directory, the permissions turn to 

d??????????   ? ?    ?          ?            ?

they show up as being owned by root when ls -l  is ran as root. 


Version-Release number of selected component (if applicable):
Fedora 24

How reproducible:
100% 

Steps to Reproduce:
1. iFuse <dir>
2. can't cd into directory unless root
3. gvfs-afc only mounts Documents on iPod

Actual results:


Expected results:


Additional info:

I tried adding my user to /etc/group under usbmuxd. Didn't do anything.

Comment 1 Peter Robinson 2016-04-08 20:00:28 UTC
(In reply to rosenp from comment #0)
> Description of problem:
> I feel that this is an iFuse problem. When I mount the iPod as root to any
> directory, the permissions turn to 

Why iFuse? It's not used by gvfs-afc what so ever

Comment 2 rosenp 2016-04-08 20:24:43 UTC
huh? I thought gvfs-afc used iFuse.

Anyway, if it really doesn't, then I guess there are 2 issues: permission issues with iFuse and gvfs-afc not mounting the iPod. The latter being the more important one.

Comment 3 rosenp 2016-04-08 20:34:36 UTC
Created attachment 1145250 [details]
log from journalctl

i can't see anything useful from journalctl but here it is anyway