From: Christiaan H. <cmh...@gm...> - 2009-03-10 11:15:53
|
On 10 Mar 2009, at 4:34 AM, ski...@re... wrote: > Hi list, > > I continue to have the following problem and can't figure out what is > causing it: > > When I change the default application to view PDF files to Skim (File > Info -> Open with ... / Change all), Skim becomes the default viewer > for PDFs for the current session. After logging out and back in, the > default Application has been reset to Preview.app. Each time I login, > I have to redo these steps. And that pretty much annoys me. > > I am administering my system by myself, no-one else is messing with > it, so there must be something wrong in the system. I don't think the > bug is on Skim's side, but I was hoping that someone else might have > experienced something similar and might have some advice. Here is a > summary of what I have tried (of course I have checked all sorts of > mailing lists and google and the like, but without success): > > Performing a "defaults read com.apple.LaunchServices" gives me > { > LSHandlers = ( > { > LSHandlerContentType = "com.adobe.pdf"; > LSHandlerRoleAll = "net.sourceforge.skim-app.skim"; > } > ); > } > pretty much the same before and after changing the default setting for > PDFs as above. That looks alright to me. But apparently it can't be > the correct place where MacOS stores the information of what > Application to use for what file type. Does anybody happen know where > that information would be hidden? > > Deleting /Library/Caches/com.apple.LaunchServices-*.csstore helped > once for one single relogin, but that can't be a long-term solution > either, if I have to do that again and again every time I log in. > > I suspect that this strange effect might have to do with my encrypted > home directory, since that is probably something not many people would > use. If anybody does use it as well and has no problems with setting > Skim as the default PDF viewer, please let me know. Otherwise I can't > see what I am doing so different from other Skim users. > > Any thought's what else I could try?! Anything is appreciated! > > Cheers > > Bjoern > > --- > MacOS 10.5.6, Skim Version 1.2.1 (39) > Strange, I've never heard of this. If you can you should file a bug report with Apple about this, because it's obviously a bug somewhere in the system. Have you tried resetting your launch services cache? Type the following in Terminal.app on a single line: System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/Support/lsregister -kill -r -all local,user,system Christiaan |