Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upLatest Update says Ascension can't open files of type .nfo #6
Comments
ghost
assigned
ByteProject
Aug 25, 2012
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ByteProject
Aug 25, 2012
Member
Can't reproduce the issue here. Tried it on three different Macs all running 10.8.1 and Ascension opens NFO's just fine. Here's a screenshot of Ascension 2 running on ML 10.8.1. Anyway, I probably know where your problem is originating from. Could it be another tool for handling NFO's is improperly registering with LaunchServices and thus conflicting with Ascension? It could also be your LaunchServices database is corrupted.
You can force an application to re-register file types for that application using the -f option followed by the application path. For example, to re-register Ascension (Terminal):
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -f /Applications/Ascension.app
You can also unregister a specific application using the -u option.
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -u /Applications/Conflicting.app
You may try to unregister Ascension as well it will re-register upon next launch. Please wipe ANY conflicting apps as well.
The lsregister command is actually just a front-end management tool for the ~/Library/Preferences/com.apple.LaunchServices.plist file. The file’s contents can be read (in an unparsed form) using defaults:
defaults read ~/Library/Preferences/com.apple.LaunchServices
The database can be a pretty fat beast over time. You can completely clean and rebuild it with the following command:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
You can also set Ascension to open NFO's by doing the following:
defaults write com.apple.LaunchServices LSHandlers -array '{ LSHandlerContentType = "nfo"; LSHandlerRoleAll = "com.byteproject.ascension"; }';
My suggestion is: you should completely clean and rebuild the database. Make sure any conflicting apps are wiped. If not an option, unregister conflicting apps manually (if wiped from your disk, they're still in the database) and unregister Ascension (it will automatically re-register next time you launch it). You can optionally register Ascension for NFO's with the last command.
Please reply ASAP so I know if it works for you. I probably should create a FAQ here on the repository for common issues. I once had the same issue you have now (yes!) and I searched like insane until I found a proper solution.
|
Can't reproduce the issue here. Tried it on three different Macs all running 10.8.1 and Ascension opens NFO's just fine. Here's a screenshot of Ascension 2 running on ML 10.8.1. Anyway, I probably know where your problem is originating from. Could it be another tool for handling NFO's is improperly registering with LaunchServices and thus conflicting with Ascension? It could also be your LaunchServices database is corrupted. You can force an application to re-register file types for that application using the -f option followed by the application path. For example, to re-register Ascension (Terminal): You can also unregister a specific application using the -u option. The lsregister command is actually just a front-end management tool for the ~/Library/Preferences/com.apple.LaunchServices.plist file. The file’s contents can be read (in an unparsed form) using defaults: The database can be a pretty fat beast over time. You can completely clean and rebuild it with the following command: You can also set Ascension to open NFO's by doing the following: My suggestion is: you should completely clean and rebuild the database. Make sure any conflicting apps are wiped. If not an option, unregister conflicting apps manually (if wiped from your disk, they're still in the database) and unregister Ascension (it will automatically re-register next time you launch it). You can optionally register Ascension for NFO's with the last command. Please reply ASAP so I know if it works for you. I probably should create a FAQ here on the repository for common issues. I once had the same issue you have now (yes!) and I searched like insane until I found a proper solution. |
ByteProject
closed this
Aug 31, 2012
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
prophetizer
Sep 4, 2012
rebuilding the database worked, thanks!
PRoPHeTiZeR
prophetizer@bluntz420.com
On Aug 25, 2012, at 12:53 AM, Stefan Vogt notifications@github.com wrote:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
prophetizer
commented
Sep 4, 2012
|
rebuilding the database worked, thanks! PRoPHeTiZeR On Aug 25, 2012, at 12:53 AM, Stefan Vogt notifications@github.com wrote:
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
aww wonderful :) |
prophetizer commentedAug 25, 2012
it won't open NFO's on mountain lion with the new mountain lion update to 2.0.6 (95)
i have tried on 2 different macs, with the same effect