Spotlight issue -- preferences ignored

Hi, I have another issue that can be added to the growing list of spotlight issues:
I UNCHECK "mail messages" in the list of files types under "search results" preferences for spotlight, and these still show up in my search results.
Also, when I select the order of files types, it is ignored in the window with results that pops up after choosing showa all...
Any ideas what is going on?
Thanks,
Artur

I actually meant the folder where most preferences are usually stored for the user--the one in the "hard drive>users>user>library>preferences" folder
But it should work for the system-level preference folder as well!
However, I just noticed this: You can search for preference files in the enclosing "library" folder's search window as well, so apparently you don't need to go down to the "preference" folder directory!
I still don't know why you can't search for preferences at the highest level--why do we have to drill down to a "library" window to search for preference files?

Similar Messages

  • OS X 10.8.3, TM & Spotlight Issue

    I just upgraded to OS X 10.8.3 and my TM is no longer backing up. This appears to be a Spotlight issue as all I get is Estimating Index Time when I open Spotlight.  I tried the trick of making my HD private in Spotlight then public again - same result it's still estimating index time.  I've read lots of posts about Spotlight being buggy after operating system upgrades although most are 1-2 years old.  Anyone have a solution to this?

    The pink box in #D2 of Time Machine - Troubleshooting shows how to do it on a Time Machine backup drive; use the same procedure, but apply it to your internal HD instead.
    The index is normally hidden; you need to be able to see it to delete it via the Finder.  Installing the Tinker Tool app via the link there is one way of making them visible.
    Then locate and delete the index (but the one on your Mac's HD).
    Which part of that do you need help with?

  • Spotlight issue! mdutil -i -on not working

    hi there,
    i have a serious spotlight issue:
    all my drives/partitions beside the startup volume are not indexed/searchable
    when i check with mdutil -s it tells me "indexing disabled"
    however if try mdutil -i -on /Volumes/the_disk t does not work
    also mdutil -a -i on does not enable indexing.
    and yes, i ran the commands as su.
    what is going on and more importantly:
    wtfigo?

    hey e.blofeld!
    i have the same problem (since weeks) and no idea how to solve it.
    i hope you could solve the spotlight issue. if yes, please let me know how, because it makes me nuts.
    greets

  • Issues with spotlight, system preferences, and other programs

    I am having some incredibly frustrating issues since I autoupdated last week. Since using autoupdate, My spotlight will not work (I type in information and it deletes the characters moments after i type it, and my system preferences will not open; it merely closes after 2-3 seconds. I saw on the spotlight board that to fix the spotlight, you must index the spotlight to make it work after an update, but I cannot do that because system preferences will not work. Dows anybody have any input???
    Thanks!

    I'm not sure if this helps, but here is my log in my console. I tried deleting thd files you mentioned, however it is still malfunctioning. Any other ideas???
    Thank!
    -Jc
    Mac OS X Version 10.4.4 (Build 8G32)
    2006-01-30 22:40:10 -0700
    2006-01-30 22:40:18.466 SystemUIServer[163] lang is:en
    Jan 30 22:40:23 jonathon-gables-ibook-g4 diskarbitrationd[30]: SystemUIServer [163]:17411 not responding.
    Jan 30 22:40:26 jonathon-gables-ibook-g4 crashdump[180]: mds crashed
    Jan 30 22:40:27 jonathon-gables-ibook-g4 crashdump[180]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:40:47 jonathon-gables-ibook-g4 mds[185]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:40:49 jonathon-gables-ibook-g4 crashdump[188]: System Preferences crashed
    Jan 30 22:40:50 jonathon-gables-ibook-g4 crashdump[188]: crash report written to: /Users/Jon/Library/Logs/CrashReporter/System Preferences.crash.log
    Jan 30 22:40:53 jonathon-gables-ibook-g4 crashdump[192]: mds crashed
    Jan 30 22:40:53 jonathon-gables-ibook-g4 crashdump[192]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:00 jonathon-gables-ibook-g4 crashdump[198]: mds crashed
    Jan 30 22:41:00 jonathon-gables-ibook-g4 mds[199]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:41:01 jonathon-gables-ibook-g4 crashdump[198]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:02 jonathon-gables-ibook-g4 crashdump[203]: mds crashed
    Jan 30 22:41:03 jonathon-gables-ibook-g4 crashdump[203]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:16 jonathon-gables-ibook-g4 configd[28]: SecKeychainFindGenericPassword err= -25308 ( =0xffff9d24, secErrStr=User interaction is not allowed. ) (current= ACTIONTEC)
    Jan 30 22:41:17 jonathon-gables-ibook-g4 mds[211]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:41:17 jonathon-gables-ibook-g4 crashdump[210]: mds crashed
    Jan 30 22:41:17 jonathon-gables-ibook-g4 crashdump[210]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:28 jonathon-gables-ibook-g4 crashdump[232]: mds crashed
    163: Can't create query: 0x10000003
    2006-01-30 22:41:28.698 SystemUIServer[163] /SourceCache/BullSearch-121.34/Matador-121.34/SearchItem/Models/_MDQueryAdaptor .m -[_MDQueryAdaptor _createMDQuery] Can't execute query '(* = "itunes*"wcd || kMDItemTextContent = "itunes*"cd) && _kMDItemIgnore != *'
    Jan 30 22:41:29 jonathon-gables-ibook-g4 crashdump[232]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:30 jonathon-gables-ibook-g4 mds[239]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:41:30 jonathon-gables-ibook-g4 crashdump[238]: mds crashed
    Jan 30 22:41:30 jonathon-gables-ibook-g4 crashdump[238]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:33 jonathon-gables-ibook-g4 ntpdate[228]: no server suitable for synchronization found
    Jan 30 22:41:49 jonathon-gables-ibook-g4 crashdump[282]: mds crashed
    Jan 30 22:41:50 jonathon-gables-ibook-g4 crashdump[282]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:51 jonathon-gables-ibook-g4 mds[288]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:41:51 jonathon-gables-ibook-g4 crashdump[287]: mds crashed
    Jan 30 22:41:52 jonathon-gables-ibook-g4 crashdump[287]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:52 jonathon-gables-ibook-g4 crashdump[293]: mds crashed
    Jan 30 22:41:53 jonathon-gables-ibook-g4 crashdump[293]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:54 jonathon-gables-ibook-g4 crashdump[299]: mds crashed
    Jan 30 22:41:55 jonathon-gables-ibook-g4 crashdump[299]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:56 jonathon-gables-ibook-g4 mds[306]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:41:56 jonathon-gables-ibook-g4 crashdump[305]: mds crashed
    Jan 30 22:41:57 jonathon-gables-ibook-g4 crashdump[305]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:41:58 jonathon-gables-ibook-g4 crashdump[311]: mds crashed
    Jan 30 22:41:59 jonathon-gables-ibook-g4 crashdump[311]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:00 jonathon-gables-ibook-g4 crashdump[317]: mds crashed
    Jan 30 22:42:00 jonathon-gables-ibook-g4 mds[318]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:00 jonathon-gables-ibook-g4 crashdump[317]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:01 jonathon-gables-ibook-g4 crashdump[323]: mds crashed
    Jan 30 22:42:02 jonathon-gables-ibook-g4 crashdump[323]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:03 jonathon-gables-ibook-g4 crashdump[329]: mds crashed
    Jan 30 22:42:04 jonathon-gables-ibook-g4 crashdump[329]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:05 jonathon-gables-ibook-g4 mds[336]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:05 jonathon-gables-ibook-g4 crashdump[335]: mds crashed
    Jan 30 22:42:05 jonathon-gables-ibook-g4 crashdump[335]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:11 jonathon-gables-ibook-g4 crashdump[341]: mds crashed
    Jan 30 22:42:12 jonathon-gables-ibook-g4 crashdump[341]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:13 jonathon-gables-ibook-g4 crashdump[347]: mds crashed
    Jan 30 22:42:14 jonathon-gables-ibook-g4 crashdump[347]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:15 jonathon-gables-ibook-g4 crashdump[353]: mds crashed
    Jan 30 22:42:15 jonathon-gables-ibook-g4 mds[354]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:16 jonathon-gables-ibook-g4 crashdump[353]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:17 jonathon-gables-ibook-g4 crashdump[359]: mds crashed
    Jan 30 22:42:18 jonathon-gables-ibook-g4 crashdump[359]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:19 jonathon-gables-ibook-g4 crashdump[365]: mds crashed
    Jan 30 22:42:21 jonathon-gables-ibook-g4 crashdump[365]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:22 jonathon-gables-ibook-g4 mds[372]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:22 jonathon-gables-ibook-g4 crashdump[371]: mds crashed
    Jan 30 22:42:23 jonathon-gables-ibook-g4 crashdump[371]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:24 jonathon-gables-ibook-g4 crashdump[377]: mds crashed
    Jan 30 22:42:24 jonathon-gables-ibook-g4 crashdump[377]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:26 jonathon-gables-ibook-g4 mds[384]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:26 jonathon-gables-ibook-g4 crashdump[383]: mds crashed
    Jan 30 22:42:26 jonathon-gables-ibook-g4 crashdump[383]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:28 jonathon-gables-ibook-g4 crashdump[389]: mds crashed
    Jan 30 22:42:28 jonathon-gables-ibook-g4 crashdump[389]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:29 jonathon-gables-ibook-g4 crashdump[395]: mds crashed
    Jan 30 22:42:30 jonathon-gables-ibook-g4 crashdump[395]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:31 jonathon-gables-ibook-g4 mds[402]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:31 jonathon-gables-ibook-g4 crashdump[401]: mds crashed
    Jan 30 22:42:32 jonathon-gables-ibook-g4 crashdump[401]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:34 jonathon-gables-ibook-g4 crashdump[407]: mds crashed
    Jan 30 22:42:34 jonathon-gables-ibook-g4 crashdump[407]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:35 jonathon-gables-ibook-g4 crashdump[413]: mds crashed
    Jan 30 22:42:36 jonathon-gables-ibook-g4 crashdump[413]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:38 jonathon-gables-ibook-g4 mds[420]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:38 jonathon-gables-ibook-g4 crashdump[419]: mds crashed
    Jan 30 22:42:38 jonathon-gables-ibook-g4 crashdump[419]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:40 jonathon-gables-ibook-g4 crashdump[425]: mds crashed
    Jan 30 22:42:41 jonathon-gables-ibook-g4 crashdump[425]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:41 jonathon-gables-ibook-g4 crashdump[431]: mds crashed
    Jan 30 22:42:42 jonathon-gables-ibook-g4 crashdump[431]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:43 jonathon-gables-ibook-g4 mds[438]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:43 jonathon-gables-ibook-g4 crashdump[437]: mds crashed
    Jan 30 22:42:44 jonathon-gables-ibook-g4 crashdump[437]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:45 jonathon-gables-ibook-g4 crashdump[443]: mds crashed
    Jan 30 22:42:46 jonathon-gables-ibook-g4 crashdump[443]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:47 jonathon-gables-ibook-g4 mds[450]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:47 jonathon-gables-ibook-g4 crashdump[449]: mds crashed
    Jan 30 22:42:48 jonathon-gables-ibook-g4 crashdump[449]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:49 jonathon-gables-ibook-g4 crashdump[455]: mds crashed
    Jan 30 22:42:49 jonathon-gables-ibook-g4 crashdump[455]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:42:51 jonathon-gables-ibook-g4 crashdump[461]: mds crashed
    Jan 30 22:42:51 jonathon-gables-ibook-g4 mds[462]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:42:52 jonathon-gables-ibook-g4 crashdump[461]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:03 jonathon-gables-ibook-g4 crashdump[468]: mds crashed
    Jan 30 22:43:04 jonathon-gables-ibook-g4 crashdump[468]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:04 jonathon-gables-ibook-g4 mdimportserver[467]: sniffer can't check in... 1102
    Jan 30 22:43:05 jonathon-gables-ibook-g4 crashdump[474]: mds crashed
    Jan 30 22:43:06 jonathon-gables-ibook-g4 crashdump[474]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:08 jonathon-gables-ibook-g4 mds[481]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:43:08 jonathon-gables-ibook-g4 crashdump[480]: mds crashed
    Jan 30 22:43:09 jonathon-gables-ibook-g4 crashdump[480]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:10 jonathon-gables-ibook-g4 crashdump[486]: mds crashed
    Jan 30 22:43:10 jonathon-gables-ibook-g4 crashdump[486]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:12 jonathon-gables-ibook-g4 mds[493]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:43:12 jonathon-gables-ibook-g4 crashdump[492]: mds crashed
    Jan 30 22:43:12 jonathon-gables-ibook-g4 crashdump[492]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:13 jonathon-gables-ibook-g4 crashdump[498]: mds crashed
    Jan 30 22:43:14 jonathon-gables-ibook-g4 crashdump[498]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:15 jonathon-gables-ibook-g4 mds[505]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:43:15 jonathon-gables-ibook-g4 crashdump[504]: mds crashed
    Jan 30 22:43:15 jonathon-gables-ibook-g4 crashdump[504]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:17 jonathon-gables-ibook-g4 crashdump[509]: mds crashed
    Jan 30 22:43:17 jonathon-gables-ibook-g4 crashdump[509]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:18 jonathon-gables-ibook-g4 crashdump[515]: mds crashed
    Jan 30 22:43:19 jonathon-gables-ibook-g4 crashdump[515]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:21 jonathon-gables-ibook-g4 crashdump[521]: mds crashed
    Jan 30 22:43:21 jonathon-gables-ibook-g4 mds[522]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:43:22 jonathon-gables-ibook-g4 crashdump[521]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:23 jonathon-gables-ibook-g4 crashdump[527]: mds crashed
    Jan 30 22:43:23 jonathon-gables-ibook-g4 crashdump[527]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:24 jonathon-gables-ibook-g4 crashdump[533]: mds crashed
    Jan 30 22:43:25 jonathon-gables-ibook-g4 crashdump[533]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:26 jonathon-gables-ibook-g4 mds[540]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:43:26 jonathon-gables-ibook-g4 crashdump[539]: mds crashed
    Jan 30 22:43:26 jonathon-gables-ibook-g4 crashdump[539]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:27 jonathon-gables-ibook-g4 crashdump[545]: mds crashed
    Jan 30 22:43:28 jonathon-gables-ibook-g4 crashdump[545]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:29 jonathon-gables-ibook-g4 crashdump[551]: mds crashed
    Jan 30 22:43:30 jonathon-gables-ibook-g4 crashdump[551]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:31 jonathon-gables-ibook-g4 mds[558]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:43:31 jonathon-gables-ibook-g4 crashdump[557]: mds crashed
    Jan 30 22:43:31 jonathon-gables-ibook-g4 crashdump[557]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:32 jonathon-gables-ibook-g4 crashdump[563]: mds crashed
    Jan 30 22:43:33 jonathon-gables-ibook-g4 crashdump[563]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:34 jonathon-gables-ibook-g4 mds[570]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:43:34 jonathon-gables-ibook-g4 crashdump[569]: mds crashed
    Jan 30 22:43:34 jonathon-gables-ibook-g4 crashdump[569]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:45 jonathon-gables-ibook-g4 crashdump[576]: mds crashed
    Jan 30 22:43:47 jonathon-gables-ibook-g4 crashdump[576]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:48 jonathon-gables-ibook-g4 crashdump[581]: mds crashed
    Jan 30 22:43:48 jonathon-gables-ibook-g4 mds[582]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:43:49 jonathon-gables-ibook-g4 crashdump[581]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:43:59 jonathon-gables-ibook-g4 crashdump[588]: mds crashed
    Jan 30 22:44:00 jonathon-gables-ibook-g4 crashdump[588]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:00 jonathon-gables-ibook-g4 mdimportserver[587]: sniffer can't check in... 1102
    Jan 30 22:44:01 jonathon-gables-ibook-g4 crashdump[594]: mds crashed
    Jan 30 22:44:02 jonathon-gables-ibook-g4 crashdump[594]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:03 jonathon-gables-ibook-g4 mds[601]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:44:03 jonathon-gables-ibook-g4 crashdump[600]: mds crashed
    Jan 30 22:44:03 jonathon-gables-ibook-g4 crashdump[600]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:04 jonathon-gables-ibook-g4 crashdump[606]: mds crashed
    Jan 30 22:44:05 jonathon-gables-ibook-g4 crashdump[606]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:06 jonathon-gables-ibook-g4 crashdump[612]: mds crashed
    Jan 30 22:44:06 jonathon-gables-ibook-g4 mds[614]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:44:07 jonathon-gables-ibook-g4 crashdump[612]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:18 jonathon-gables-ibook-g4 crashdump[620]: mds crashed
    Jan 30 22:44:19 jonathon-gables-ibook-g4 crashdump[620]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:19 jonathon-gables-ibook-g4 mdimportserver[619]: sniffer can't check in... 1102
    Jan 30 22:44:20 jonathon-gables-ibook-g4 mds[627]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:44:20 jonathon-gables-ibook-g4 crashdump[626]: mds crashed
    Jan 30 22:44:20 jonathon-gables-ibook-g4 crashdump[626]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:21 jonathon-gables-ibook-g4 crashdump[632]: mds crashed
    Jan 30 22:44:22 jonathon-gables-ibook-g4 crashdump[632]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:23 jonathon-gables-ibook-g4 crashdump[638]: mds crashed
    Jan 30 22:44:23 jonathon-gables-ibook-g4 mds[639]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:44:23 jonathon-gables-ibook-g4 crashdump[638]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:24 jonathon-gables-ibook-g4 crashdump[644]: mds crashed
    Jan 30 22:44:25 jonathon-gables-ibook-g4 crashdump[644]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:26 jonathon-gables-ibook-g4 mds[651]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:44:26 jonathon-gables-ibook-g4 crashdump[650]: mds crashed
    Jan 30 22:44:26 jonathon-gables-ibook-g4 crashdump[650]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:37 jonathon-gables-ibook-g4 crashdump[657]: mds crashed
    Jan 30 22:44:37 jonathon-gables-ibook-g4 crashdump[657]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:38 jonathon-gables-ibook-g4 crashdump[663]: mds crashed
    Jan 30 22:44:39 jonathon-gables-ibook-g4 crashdump[663]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    Jan 30 22:44:40 jonathon-gables-ibook-g4 mds[670]: Excessive crashes on /.Spotlight-V100.
    Jan 30 22:44:40 jonathon-gables-ibook-g4 crashdump[669]: mds crashed
    Jan 30 22:44:40 jonathon-gables-ibook-g4 crashdump[669]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log

  • Mail alert sounds too loud; preferences ignored

    After I upgraded to Leopard, suddenly the alert sounds in Mail were way too loud. I double-checked my "Alert volume" setting in the Sound preferences and it was set low. Other system sounds are played at an appropriate level. Only Mail ignores it. It seems that no matter what my system volume is set to, Mail alerts are played at 100% volume.
    I found this old thread on the same topic, and am wondering if there is any fix for this problem yet?
    http://discussions.apple.com/message.jspa?messageID=7058243
    Since I have been unable to find any reference to a fix from Apple, and I am sick of about jumping out of my skin when I am concentrating on work and a new message comes in... here is a hack that I did today that might help others: I located each sound file Mail uses (I have several that are used in my Rules), opened each in Audacity ( http://audacity.sourceforge.net/ ), adjusted each to -15db, and saved a copy of the files. I then assigned the "new mail" sound to use the quieter copy. Each rule also had to be edited to attach to the new files.
    It's a hack, and time-consuming, but it seems to work.
    Message was edited by: PeakD

    Same issue here. Been looking for a fix. . .

  • Slow Yosemite, partially solved; nagging spotlight issues

    Since I have upgraded to Yosemite, I felt like I was using Windows 95: Services regularly in an unresponsive state, spinning ball all the time with the computer freezing for 5 seconds at a time, Mission Control not showing up, etc.
    From this forums, someone suggested that I may have incompatible software, so I looked more closely and started to disable various kernel extensions, etc.
    Things got better when I got rid of
    - Pace drivers and updated them
    - CleanMyMac 2
    Then I still had some services stuck, especially CoreAudio; another thread suggested that it may be the program 'Hear'.
    - Hear... gone...
    The mac worked better; Mission control started working again after I deleted most of my profile data.
    But there were still some issues and the computer was just slow.. I had a lot of error in the console with spotlight trying to index files owned by a user that doesn't exist; I removed those files and it was like having a new computer.
    But still a slow new computer...
    I looked more closely at spotlight's activity and I found that it is indexing a lot of things I really don't want it to index. I am using Logic Pro a lot and the last thing I want is the hard drive to be busy during recording.
    I disabled Spotlight to see and, yes! the computer became faster. So I added a lot of folders in the privacy section, in Spotlight settings, but I am finding that it totally ignores some of them.
    I do NOT want it to index /Library and /Users/me/Library; I added those, but they are still getting indexed.
    I am thinking about pr

    Bump. Any ideas?

  • AAM Install Location Preference Ignored... Again!

    I have a cloud subscription, so this refers to the AAM downloader/installer.
    Having had issues previously, I double checked that the preference location for where AAM is to install a new application was set.
    After over an hour of downloading, installing & rebooting where do I find the newly installed app?
    That's right -- in the same location as every other default -- c:\ program files
    Of course, that's not where I set the AAM preference location.  
    So it appears that Adobe's App Manager has a mind of its own.
    Not only does it fail to allow you to set the preference for the very first app you install, but it also will completely ignore the fact you set it at all.
    Now back to uninstalling and trying the darn thing again. Maybe I'll get lucky and have it recognize that I don't want the installs to reside in the default location.
    More wasting time when I could be actually using the tools I purchased. Ugh.
    Anyone else experience this?  Maybe I'm missing some magic set of keystrokes or something.
    Thanks,
    -Bonnie

    After trying once more to install LR 4.1 via AAM w/ the install location preference set and having it default again I decided to "chat" with Adobe.
    Here's a portion of that chat:
    Adobe Chat Support: Since we lightroom 4 was not a part of creatiw cloud, when the CCMwas released in ,6dobe. After releasing the CCM the lightroom 4 was included in the CCM.
    Adobe Chat Support: And the lightroom 4 installer is build separately from other software and the software will be get installed, in the location where the operating s tem is installed.
    Adobe Chat Support: That is the reason you can install other software in your preferred location but not the lightroom 4, because the installer for lightroom 4 is different
    Adobe Chat Support: Though it will be with the CCM .like the other software, but it has a separate build in installer for ifs own and it can be installed in default location.
    Adobe Chat Support: Also we recommend you to install the software in the default location, because sometimes you might get any errors while using the software.
    So according to support we all should install in the default location.
    After wrangling around this issue for several installs, uninstalls, and re-installs I've found out a few things that differ from the above.
    1) With other CC (Creative Cloud) apps, you can set the AAM (Adobe Application Manager) preference for install location and they will install to that location.
    2) If you download from the CC website to begin your install before the AAM preference is set you will not have the opportunity to set it (or check that its set) and the install will go to the default location. [Open AAM from the desktop instead, check the preference, then download & install either from the website or directly thru AAM.]
    3) Uninstalling an app via control panel, rebooting, then checking AAM will display the option to Install in the AAM. (Sometimes folks have had issues where AAM seems to have gotten out of synch w/ their cloud app installs. This has consistently worked for me to keep them aligned -- i.e. always reboot after uninstalling before heading into AAM for another install.)
    4) LR install/upgrade behavior differs from other CC apps.
          a) AAM installs of LR 4.1 do not follow the preference for install location, they will only install to the default location.
          b) If you install LR 4.1 from AAM, but want to upgrade to 4.2 you *can* set the default location to a new place for the 4.2 install.  The LR 4.1 app displays a prompt for the update, you click the link to go to the download, download it directly from the web, then run the 4.2 downloaded file. Choose the desired location (different from where 4.1 is currently installed) and complete the install process.  Register the app as prompted.
    5) Adobe Acrobat X will install to the preference directory directly from AAM, however it will complain of not being licensed upon restart. (This could be because my internet connection was not up during its first pass at registration.)
           a) Upon seeing the license dialog which asked if I wanted to try or buy, I clicked try. Upon entering my adobeID it went to the internet to validate the ID and also appears to have validated the install.
    So, at this point I'm hoping I have resolved my installation issues and have successfully installed both LR 4.2 and Acrobat X to non-default directories.
    I am also hopeful neither is being considered by the system as "trial" software -- I'll see if the trial screen pops up for either in the future.
    The next question is -- can I uninstall LR 4.1 from the default location wtihout it impacting my LR 4.2 install. I hope so, but I'll save that for another day!
    So for anyone out there with AAM CC install issues -- hopefully this is of some help.   I know I certainly didn't find Adobe chat all that enlightening -- I got more out of my own trial & error. Sad.
    Cheers,
    -Bonnie

  • Finder sidebar / spotlight issue

    Hi
    I'm running os x 10.4.11 on an old quicksilver machine.
    For some reason when i open up Finder, i can no longer see any of the options in the Sidebar - yet when i move the mouse over them, they're there (cept invisible!!). Tried looking in Preferences, but this won't open .
    Also Spotlight seems to have given up... even simple searches are returning "nada"...
    Anyone else had this weird (but increasingly problematic) issue??
    Thanks
    Damien

    Hi again. Perhaps some maintenance would be good!
    Boot from your Install Disk, and select your Language. Do not press continue.
    Click the little arrow at the bottom of that page.
    When the Window opens, look up top at the Menu Bar, and select Utilities.
    A menu will open, from this select Disk Utility.
    Select your HD from the list on the left (the first one)
    Click the First Aid tab, and Repair Disk. Reboot.
    Now, from your Applications Folder, select Utilities>Disk Utility
    Select the HD, click First Aid, and Repair Disk Permissions.

  • Solutions to Some DNS, OD, AFP, CalDAV, AFP, and Spotlight Issues

    I recently upgraded our aging Xserve (1.3GHz G4, yeah baby!) to Leopard Server from Tiger Server so everything in the office would all be on the same OS. This server hosts all our in-use files via an Xserve RAID, and our dead files are on the internal 3-disk striped array. It's also the Open Directory master and hosts the office's DNS (I wanted to put OD and DNS on the new Xeon Xserve that hosts our FileMaker database, Retrospect backup, and our Squid web proxy, but something in its DNS configuration is broken and I gave up on that since OD and DNS don't really put any additional stress on the G4). Anyway, with all the hoopla of configuring, reconfiguring, and fixing, I've learned some things that may help others.
    *DNS, Open Directory, and AFP*
    I had some trouble with groups and ACL permissions, inability to get CalDAV working, and general strangeness with OD and Workgroup Manager. Demoting the server from an OD master to standalone took care of most of these. Part of the problem was an incorrect LDAP search base, which can only be corrected by blowing away the OD master and making sure DNS is set up properly. We only have about 20 users (we don't host network homes or anything like that), so when I did the demotion I just let it destroy all the accounts, and after promoting the server back to an OD master, I recreated the users and groups from scratch. So with freshly created users and groups, and after resetting the ACL's and propagating permissions on the network shares, that cleared up the permissions problems. The corrected LDAP search base fixed the Directory application too, which wasn't showing any contacts before, and it got Kerberos working as well.
    iCal/CalDAV
    All this work also got CalDAV/iCal calendar sharing running, and when I enable calendaring for a user, it stays enabled in WGM. Before, whenever I'd switch to another user and come back, calendaring would be turned off in WGM, although it was in fact still enabled. I haven't tested calendaring much yet, and adding an account in iCal is still a bit flakey. Our DNS is just internal, so in Server Admin I un-checked "fully-qualified" for our few DNS hostnames. If I mark the server's DNS hostname as fully-qualified, auto-discovery of the address in iCal won't work. iCal rejects my passwords if Kerberos authentication is used in either case, even if I manually point it to the IP address, but it connects fine without Kerberos.
    *Spotlight and AFP*
    Another problem I had after upgrading the server was stale spotlight searches. I used Server Admin to turn spotlight searching on and off for the two shares, and I tried any number of mdutil commands and System Preferences "privacy" settings to turn indexing on and off and to rebuild the indexes. With the old machine and about a terabyte of data, indexing would take all night, so I couldn't really try a lot of things. Every time the index was rebuilt, it would propagate out to the office just fine, but it would never update from then on. The solution to that was changing the permissions on the volumes the shares are on. The shares themselves had the correct permissions and ACL's, but the volumes need their POSIX permissions set to:
    owner: root: read/write/execute
    group: admin: read/write/execute
    everyone: read/execute
    Over the years those permissions had been changed (this server started out with OS X 10.2 Server btw, so there's been plenty of time for things to get b0rked), but Tiger Server apparently didn't care. Another thing I did (although I'm not sure if this was necessary) was to change the "Others" POSIX permission from None to Read Only. Once all that was changed, mdworker started chugging along to keep the spotlight index updated. However, it went nuts after the 10.5.6 Server update, constantly working with no sign of ever finishing. The update notes do make specific mention to Spotlight changes, which says you have to disable spotlight indexing for any shares in Server Admin, then re-enabled it to "take advantage of the new features." That started another night of indexing, but it's now done and updating properly. I noticed that a new inherited ACL for the user "Spotlight" showed up at the root level of each share point. I'm not going to touch that.
    I'll admit that I hate spotlight's interface and lack of control in Leopard (i.e. it always resets your search parameters, you can't change the results window's columns, and you have to already be in the folder you want to search, etc.). That being said, I can search for anything on the server and it finds the results almost instantly. Even a search that returns "more than 10,000" results only takes about 5 seconds. With Tiger or Panther server, ANY search would take several minutes and grind the server to a halt, making anyone else who tried to save a file or navigate the shared volumes get the spinning beach ball.
    Hopefully this will be of help to someone.

    Hi.
    You've not outlined your issues with AFP per se, having any ?
    DNS is critical for OS X Server, it's appropriately finicky about working forward & reverse DNS lookup for its FQDN.
    Certainly, Leopard Server may make assumptions contrary to your intent, if using the non-advanced setups, as it will attempt to use DNS and if not available, this may result in settings other than you desire.
    By default, hostnames entered in the Server Admin DNS settings, will be considered as part of the DNS zone you're editing.
    So:
    server
    would be for: server.yourfqdn.com
    If you mark that as fully qualified, well, then it's looking for: server
    which is not a FQDN
    As well, I believe Apple states it should no longer be necessary, but if you do need to change the hostname for your OD master, it is often possible via the Termina/command-line via:
    (sudo) changeip
    http://developer.apple.com/documentation/Darwin/Reference/Manpages/man8/changeip .8.html

  • Status keeps changing from invisible to online: why the issue is ignored?

    There is a serious issue raised in the parallel thread, which is critical for many people: "Status keeps changing from invisible to online" (initiated on ‎16-11-2014 by b.agne, Mac section). In short, when starting using a device, the Skype status changing from "invisible" to "online" - sometimes just for a moment, though enough for others to notice you. These affects very much any type of devices. I am sure the issue has already led to multiple personal crisises and potentially financial losses due to buseness partnership issues (I came close to that myself, and now use anything but Skype for business). The question is: WHY the issue is completely ignored by Skype, Microsoft and expert comunity? Please post the solution if anybody knows how to fix the issue, or suggest how to make Microsoft to know that it should be fixed. Kind regard...

    Hi, I also have the same issue. I change the status to Invisible and a later on it is already as "Online", without having even touched/opened Skype. The only way that I see this may happen is that I have the app installed on the smartphone, but before it never had this issue, but from some month ago it started. Any correction or suggestion to work around this issue? Regards

  • 10.5.8 Server / severe Spotlight issues

    Hello everybody,
    i am currently experiencing quite some problems with Spotlight on 10.5.8 Server:
    - Spotlight is running
    - the Network Shares are all Spotlight enabled
    - sudo mdutil -s -a shows all Network Shares as indexed
    - When running a search directly on the server, everything seems to be ok. When running a search on a client (CMD+F) and searching inside a folder on a network share, search results are shown, but when trying to open them, i get an errormessage stating that the alias can´t be opened as the original file can´t be found. When conducting the same search on the server, everything seems to be fine
    What i´ve tried until now:
    - restarting spotlight server
    - reindexing all network shares
    - reindexing the client machines
    - checked permissions
    Nothing seems to help. Is there any possibility to reset the whole spotlight search system?
    Thanks a lot for your help
    Tobias

    I was wondering if you found a solution for the search issue? We're having the same issues as well.
    Thanks!

  • Spotlight Issues

    Hey I am having an issue with spotlight on a network at home before i tiger I use to be able to explore network drives using spotlight. The network drive is on another computer in the office which use to work fine before upgrading to Leopard. Main Question*+ When I open up one of the external drives attached to another co-workers computer from my computer and use the search function it says "searching "This Mac"". And nothing ever opens

    I have a similar, but slightly more annoying issue.
    Every once in a while (seemingly at random), Spotlight decides that all my drives need to be indexed again (not just when I restart). I have an internal 250GB, an external Firewire 250GB, an external USB 250GB and a 500GB USB that is used for my Time Machine.
    Anyway, about two or three minutes into Spotlight indexing these drives, I get a Kernel Panic and have to restart. To prevent this, as soon as Spotlight starts indexing I have to quickly throw all drives into the Privacy area to stop them from being indexed, and then release them one by one back to Spotlight to be indexed. This takes really long and is very annoying.
    One other, possibly related issue, is that Spotlight doesn't work under Time Machine. Whenever I use Time Machine, no matter what I put in the search window, it returns no results.
    Any ideas anyone?
    Thanks,
    Paul C.
    Message was edited by: unicorn27

  • Mac Newbie TM & Spotlight issues

    Hi All,
    I got my new iMac on 21 September 2012.  I have a NAS (Network Attached Storage) drive on my Netgear DGN 2200 router which Spotlight never really managed to index - it always estimates a huge amount of time and even if I let it go it doesn't get it done. 
    When I started TM backup it extimated about a month and I let it go because I thought it would figure out that it was a new / empty machine quite quickly and the estimate would come down.  After two days and only 2-3GB backed up I stopped it and deleted all of the backup data and started again.  Same issue.
    Then I turned off spotlight and eventually got a week-long backup done. 
    I then updated to 10.7.5 supplemental upgrade which apparently fixes long TM backup issues. 
    Now, with spotlight turned back on TM has been taking forever with its incremental backups.  For example, I turned it on an hour ago and opened pages & Chrome, then it started a backup 50 minutes ago.  It says "Backing up: 116.6 MB of 116.6 MB" but it's still going 50 MINUTES later!!!  update: 75minutes later
    Spotlight is still not indexing my external storage which is an issue because I have all of my work on the external.
    I have been trawling through this forum but being a mac newbie I don't understand all of the jargon - sudo this and that, and if I get a solution it does need to be step by step.  I have always been tinkering around under the hood of previous M$ machines and would be a 'power-user' so I'm not stupid but it's a whole new language for me.
    Should I upgrade to Mountatin Lion?
    Is there any way I can downgrade to 10.6?
    Is there any way to search without using spotlight?  On the pc I used to be able to search non-indexed locations, it would just take a little while.
    Time Machine is not trying to backup my NAS drive is it?  From my understanding it doesn't do that but maybe it's confused ... ???
    Thanks for your help.

    I don't use raid myself so I'll leave that explanation to others. I configure my Mac Pro with 4 drives. My main drive is my boot drive and has about 300+ gigs free. I have a backup drive for that which I use SuperDuper for backup, creating a fully bootable backup drive in the event my main drive has a problem. I only back up to that drive when my machine is "good and solid". That allows me to throw on the most recent update without much concern. If there is a problem then I just boot from my backup drive and I'm back up and running just fine. I also use the backup of my main drive for my Final Cut Pro scratch drive. I copy the files for my movies to external drives for archive when needed. For my data drives I use another set of 500 gig drives. One for data (mostly photos) and one to backup using superduper whenever I feel like it. You could automate it all with Retrospect for the data drives if you wanted to. I don't think Retrospect will make a bootable backup of a main drive. I use Western Digital WD5000KS ddrives, 500 megs each. They make another model for those wanting RAID. Set up RAID, by all means, if squeeking every ounce of speed is your goal to be sure. My setup is conservative, redundant and very safe. A simple search here or on google for RAID0 or such will turn up much info on raid configuations.

  • Spaces and Spotlight issues after wakeup

    Hi, when ever I wakeup my macbook pro 13" running 10.6.8 I have 2 issues:
    1)  the spaces grid freezes on the screen. I can still navigate via apple key + arrow keys, but the grid wont dissappear until...
    2) I fidgit with spotlight. It wont respond via apple key + spacebar. I have to click on the magnifying glass. The keys I type aren't displayed in the box but the escape key works after some few times pressing it.
    Then once i do that, i can use spotlight via keyshorcut, and the spaces grid will disappear. Has anyone else experienced this?
    Thanks.

    Your slow Time Machine problem may not have to do with the kernel panic. Many people are reporting very slow Time Machine backups, and it is generally thought it is because Spotlight is hung up. (Time Machine relies on Spotlight to help track what files changed for the next backup.) Here's the thread, which I'm following because I have the same problem.
    https://discussions.apple.com/message/19679273#19679273

  • Spotlight issue - Finder comments dont seem to be updated

    Hi,
    trying to classify files using spotlight comments in the Finder (after Cmd-i; also via AppleScript) but it's hit&miss. Usually (not always) adding a comment works and a search finds it immediately, but sometimes it does not. The other way is worse: removing a comment very often is not taken into account at all - the file remains in the respective Saved Search, even though Cmd-i shows that the comment is gone.
    Some more datapoints:
    - reindexing helps; mdutil -E <VolumeName>, wait 30min, and then everything is fine (...this is a bit of a Windows solution...)
    - mdls has the wrong information, ie even if the comment is gone from the file it still is in mdls (...which makes sense I guess; this is why the search still finds it...)
    - mdimport -d 2 <filename> shows that the correct comment (eg no comment, or a changed comment) has been read, it is just ignored (ie subsequent mdls shows the old comment)
    I guess this is a bug, so I can really only hope Apple will fix it - but does someone know a workaround that would force spotlight to import all data? I guess it is one of the Apple optimisation tricks- OSX thinks it knows better....

    what always helps for me is to run from a terminal
    mdutil -E /Volumes/Volumename
    which rebuilds the index (Volumename is the name of a mounted encrypted sparsebundle) --- but this is slow
    what sometimes helps is to eject / remount the disk, but no clear solution yet
    Oh, and by the way: on a 1GB drive (mainly pdfs) my freshly indexed spotlight is 100MB, but after a week or so it grows to 900MB...)

Maybe you are looking for