Re: [Tracker] tracker-miner-fs stuck Initializing

[Martyn Russell <martyn lanedo com>]

On 31/10/13 12:09, Brian J. Murrell wrote:
> On 10/29/2013 09:31 AM, Carlos Garnacho wrote:

Hello Brian,

> > I think the output of gvfs-mount -l would be useful here.
>
> Drive(0): SAMSUNG SV1204H
>    Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
>    Volume(0): PRESARIO
>      Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
>    Volume(1): PRESARIO_RP
>      Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Drive(1): ST3500418AS
>    Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
>    Volume(0): 4.0 GB Volume
>      Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Drive(2): SONY    CD-RW  CRX215E5
>    Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
> Drive(3): HL-DT-STDVD-RAM GH22NS30
>    Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
> Volume(0): Android Phone
>    Type: GProxyVolume (GProxyVolumeMonitorMTP)
>    Mount(0): Android Phone -> mtp://[usb:001,007]/
>      Type: GProxyShadowMount (GProxyVolumeMonitorMTP)
> Volume(4): 13 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(5): 13 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(6): 45 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(7): 10 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(8): 13 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(9): 13 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(10): 675 MB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(11): 13 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(12): 675 MB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(13): 4.3 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(14): 11 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(15): 107 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(16): 5.4 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(17): 159 MB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(18): 2.1 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(19): 11 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(20): 2.7 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(21): 2.7 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(22): 3.7 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(23): 54 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(24): 48 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Volume(25): 2.1 GB Volume
>    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
> Mount(1): mtp -> mtp://[usb:001,007]/
>    Type: GDaemonMount

We suspect it's the MTP mount. Can you try to start tracker without that 
mounted to see if this makes any difference?

We're still trying to figure out what is causing this. Thank you for the 
help so far.

--
Regards,
Martyn

Founder & Director @ Lanedo GmbH.
http://www.linkedin.com/in/martynrussell