diff options
| author | Andrés G. Aragoneses <knocte@gmail.com> | 2015-06-26 16:52:52 +0200 |
|---|---|---|
| committer | Andrés G. Aragoneses <knocte@gmail.com> | 2015-06-26 16:52:52 +0200 |
| commit | 70e09f8b843cb721cf36331a7d557593fc87a568 (patch) | |
| tree | 7616f93111667a4c5e9054ff3f11a990e483a06f /README | |
| parent | 857e7252c2fd02c6c2d2ad96716d9b503cf8c013 (diff) | |
| download | libmtp-70e09f8b843cb721cf36331a7d557593fc87a568.tar.gz | |
README: mention another gvfs monitor besides the gphoto2 one
In some systems[1], the gvfs-gphoto2-volume-monitor is not
the only GVFS monitor that could be hogging the device.
[1] In particular in my Ubuntu 14.04.x LTS, this is the result
of a `ps aux | grep gvfs`:
knocte1+ 2150 0.0 0.0 196640 3204 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd
knocte1+ 2157 0.0 0.0 345660 3124 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
knocte1+ 2403 0.0 0.0 298964 5552 ? Sl jun25 0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
knocte1+ 2423 0.0 0.0 285964 3376 ? Sl jun25 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
knocte1+ 2428 0.0 0.0 212440 3456 ? Sl jun25 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
knocte1+ 2433 0.0 0.0 204936 3492 ? Sl jun25 0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor
knocte1+ 2451 0.0 0.0 433144 3636 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_spaw/1
knocte1+ 2469 0.0 0.0 124728 3036 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd-metadata
knocte1+ 2479 0.0 0.0 270376 3084 ? Sl jun25 0:00 /usr/lib/gvfs/gvfsd-burn --spawner :1.5 /org/gtk/gvfs/exec_spaw/3
knocte1+ 8648 0.0 0.0 296744 4760 ? Sl 15:11 0:00 /usr/lib/gvfs/gvfsd-http --spawner :1.5 /org/gtk/gvfs/exec_spaw/4
Diffstat (limited to 'README')
| -rw-r--r-- | README | 6 |
1 files changed, 4 insertions, 2 deletions
@@ -174,9 +174,11 @@ cannot test your solution. Then re-attach the device. - Sometimes the "gvfs-gphoto2-volume-monitor" is running on the - system and hogging the device, try something like: + Sometimes some gvfs daemons are running on the + system and hogging the device, try stopping them + with something like these commands: + killall gvfs-mtp-volume-monitor killall gvfs-gphoto2-volume-monitor Then plug in the device and issue "mtp-detect" to figure out if |