Red Fall

Q: El Cap Finder Search Bug?

So, it worked in Yosemite, but not in El Capitan.

There is a folder that has image files in it, one named "143.png", one named "1436.png" (this started out with thousands of image files, but I made a new folder to simplify it with an image attached here).

 

 

In El Capitan, in that folder:

 

 

 

- I search 143 (no quotes), BOTH files show up.

- If I search 1436 (no quotes), NOTHING shows up.

- If I search for "1436" (WITH QUOTES), the 1436.png show up.

 

BUT, in Yosemite, 1436 (NO QUOTES) shows the 1436.png file.

 

Is this just a change from Yosemite to El Capitan, or is this a bug in El Capitan? Because I've had nothing but trouble with Spotlight in El Cap also.... it won't find files I KNOW are there... I've tried using the System Preferences "Privacy" Add/Delete thing on the whole hard drive, but I still keep having issues. Does the Fusion drive have anything to do with it? It's driving me crazy because as I graphic designer with TONS of design assets on the computer, Spotlight and Finder searches are not allowing me to find files I need

 

 

 

Finder-FUKT2.jpg

iMac, OS X El Capitan (10.11.3), null

Posted on Feb 6, 2016 12:07 AM

Close

Q: El Cap Finder Search Bug?

  • All replies
  • Helpful answers

Page 1 Next
  • by Esquared,

    Esquared Esquared Feb 6, 2016 3:18 AM in response to Red Fall
    Level 6 (8,518 points)
    Mac OS X
    Feb 6, 2016 3:18 AM in response to Red Fall

    Hi,

     

    I've tried to replicate this, but I can't... These are my results:

     

    - If I search 143 (no quotes), BOTH files show up.

    - If I search 1436 (no quotes), the 1436.png shows up.

    - If I search for "1436", the 1436.png show up.

     

    So the cause must be at your end somewhere. I don't have a Fusion drive, so that may be it. But it might be something else.

     

    Have you tried replicating this in another (freshly made) user account and/or in Safe Mode?

  • by chroot,

    chroot chroot Feb 6, 2016 3:29 AM in response to Red Fall
    Level 4 (1,099 points)
    Feb 6, 2016 3:29 AM in response to Red Fall

    You can try search filtering.  Press Command + F.

     

    Screen Shot 2016-02-06 at 6.28.27 AM.png

     

    If all else fails you can grep.

  • by Esquared,

    Esquared Esquared Feb 6, 2016 4:19 AM in response to chroot
    Level 6 (8,518 points)
    Mac OS X
    Feb 6, 2016 4:19 AM in response to chroot

    Have you tried to replicate this?

  • by chroot,

    chroot chroot Feb 6, 2016 5:00 AM in response to Esquared
    Level 4 (1,099 points)
    Feb 6, 2016 5:00 AM in response to Esquared

    Yes, when using the search box the same issue happens.  When using search filtering the issue is not present.

     

    Screen Shot 2016-02-06 at 7.59.42 AM.png

    Screen Shot 2016-02-06 at 7.59.49 AM.png

  • by Red Fall,

    Red Fall Red Fall Feb 8, 2016 10:08 PM in response to Esquared
    Level 1 (5 points)
    Feb 8, 2016 10:08 PM in response to Esquared

    Esquared wrote:

    So the cause must be at your end somewhere. I don't have a Fusion drive, so that may be it. But it might be something else.

    Have you tried replicating this in another (freshly made) user account and/or in Safe Mode?

    I'm not sure what I could be doing on my end to cause this... the EXACT same folder with the EXACT same search criteria works on Yosemite but not El Capitan.

    I tried creating a new user account... same problems. I also tried adding the search criteria.

    If the original search (in the top right search bar) is 143, I can add criteria and Name > Contains > 1436 and Name > Matches > 1436 will return the expected results. If however the original search is 1436, no combination in search criteria will return the 1436.png... ***

     

    Again, when copying the same folder and running the same search on Yosemite, it just works the way you would expect... you just do a normal search without any extra search criteria and a search for 1436 returns the file 1436.png. I don't understand why it doesn't work the same way on El Capitan, but with such a large collection of design assets, it's making it very difficult to work.

     

    - Could this perhaps just be a corrupted Spotlight file?

    - Is the Spotlight search and Finder search handled differently?

    - Is there a way to totally reset either of these?

     

    It seems like if a new user account has the same problems, it's just a bug within El Capitan itself, but I'm just hoping someone with more knowledge than me has a solution.

  • by Esquared,

    Esquared Esquared Feb 9, 2016 12:01 AM in response to Red Fall
    Level 6 (8,518 points)
    Mac OS X
    Feb 9, 2016 12:01 AM in response to Red Fall

    It's all Spotlight related. You can try to reindex Spotlight: https://support.apple.com/en-us/HT201716

  • by Red Fall,

    Red Fall Red Fall Feb 9, 2016 12:32 AM in response to Esquared
    Level 1 (5 points)
    Feb 9, 2016 12:32 AM in response to Esquared

    Wel, as I stated in the first post, I've already done that to the HD, and it didn't solve the issue. Is there some Terminal command that will delete the Spotlight index file? I amy not be using the correct terminology here, but I'm assuming there is a file somewhere on the drive that stores the all the info Spotlight uses for it's searches, the index itself.

     

    I have no proof, but I'm thinking either

    a) Fusion drive itself is the culprit, since I technically have 2 HD's on the machine that the OS sees as one and it moves files I access frequently onto the SSD (I thing thats an oversimplification, but it's the way I understand it) or

         - You (Esquared), without a fusion drive, are not having the issue

    b) just some bad code somewhere in El Capitan

         - El Capitan is producing other issues (like the Adobe Illustrator CS5 crash-on-Save fiasco) https://forums.adobe.com/thread/1969084?start=0&tstart=0


    This is really aggravating. I spent a lot of money for a new iMac, and the software I use to make a living can not save without crashing, and with years worth of design assets,

  • by chroot,

    chroot chroot Feb 9, 2016 2:06 AM in response to Red Fall
    Level 4 (1,099 points)
    Feb 9, 2016 2:06 AM in response to Red Fall

    Red Fall wrote:

     

    Wel, as I stated in the first post, I've already done that to the HD, and it didn't solve the issue. Is there some Terminal command that will delete the Spotlight index file? I amy not be using the correct terminology here, but I'm assuming there is a file somewhere on the drive that stores the all the info Spotlight uses for it's searches, the index itself.

     

     

    It's stored in the /.Spotlight-V100 folder but the files for the indexing information is deleted when you add it to the Privacy tab in Spotlight.  Manually deleting this will have the same effect is adding disk to Spotlight -> Privacy.

  • by balsa2,

    balsa2 balsa2 Feb 9, 2016 2:29 AM in response to Red Fall
    Level 3 (533 points)
    Desktops
    Feb 9, 2016 2:29 AM in response to Red Fall

    Try : "name:1436" , in the top right search bar. Without the quotation marks.

  • by Red Fall,

    Red Fall Red Fall Feb 9, 2016 2:35 AM in response to balsa2
    Level 1 (5 points)
    Feb 9, 2016 2:35 AM in response to balsa2

    balsa2 wrote:

     

    Try : "name:1436" , in the top right search bar. Without the quotation marks.

    Yes, that worked, and thanks, BUT, the point remains... I didn't have to do this in Yosemite, and the guy with ElCap and no Fusion drive is NOT having this issue... So, is this a bug with the Fusion drive, or do you think some index file is corrupted? There is no way this is the intended behavior... to make it harder to search for files, where typing in an exact file name returns no results, but only if you have a fusion drive and are running El Capitan...

  • by Red Fall,

    Red Fall Red Fall Feb 9, 2016 2:37 AM in response to chroot
    Level 1 (5 points)
    Feb 9, 2016 2:37 AM in response to chroot

    chroot wrote:

     

    Red Fall wrote:

     

    Wel, as I stated in the first post, I've already done that to the HD, and it didn't solve the issue. Is there some Terminal command that will delete the Spotlight index file? I amy not be using the correct terminology here, but I'm assuming there is a file somewhere on the drive that stores the all the info Spotlight uses for it's searches, the index itself.

     

     

    It's stored in the /.Spotlight-V100 folder but the files for the indexing information is deleted when you add it to the Privacy tab in Spotlight.  Manually deleting this will have the same effect is adding disk to Spotlight -> Privacy.

     

    Ok, thanks for the info. Still, I already did it through System Preferences and it did not solve the problem

  • by balsa2,

    balsa2 balsa2 Feb 9, 2016 3:08 AM in response to Red Fall
    Level 3 (533 points)
    Desktops
    Feb 9, 2016 3:08 AM in response to Red Fall

    I don't have a Fusion drive.

    & was getting the same results as your 1st post :

    Screen Shot 2016-02-09 at 11.06.55.png

    I no longer use Yosemite.

  • by Barney-15E,

    Barney-15E Barney-15E Feb 9, 2016 4:28 AM in response to chroot
    Level 9 (50,854 points)
    Mac OS X
    Feb 9, 2016 4:28 AM in response to chroot
    It's stored in the /.Spotlight-V100 folder but the files for the indexing information is deleted when you add it to the Privacy tab in Spotlight.  Manually deleting this will have the same effect is adding disk to Spotlight -> Privacy.

    Do you know that the underlying process is exactly the same?

    I have had people here get nowhere using the Privacy pane method, but then when erasing the index using mdutil -E /, everything works again.

  • by chroot,

    chroot chroot Feb 9, 2016 4:42 AM in response to Barney-15E
    Level 4 (1,099 points)
    Feb 9, 2016 4:42 AM in response to Barney-15E

    mdutil Vol -E is the same as doing mdutil Vol -i off then mdutil Vol -i on.  It's the same as adding and removing the volume from the Spotlight preferences in the Privacy tab.  None of which will resolve the issue, I chalk it up to a logic error.

     

     

    if (2 != 2)

    {

       printf ("Why does this code block never execute?");

    }

Page 1 Next