Logos opens in a small window and flies into dock, comes back out and shuts down...never logs in. This all happens very fast. Can you offer some help! Thanks!
826515.Archive.zip
Welcome [:D]
Logos 4 Crash file shows a SQLite database file is malformed (unusable) while trying to load previously used layout that includes clippings.
Wonder about launching Logos 4 Mac to a blank layout ? wiki has => Launch to Home Page or Layout not working If blank layout launch works, could try opening a layout in Layouts menu.
Since using stable Logos 4.5b SR-1 Mac release, one [I] is contacting Logos Mac Support => http://www.logos.com/about/contact (albeit phone lines are closed on Saturday and Sunday in Bellingham, WA)
One suggestion is enabling, then posting diagnostic log files (in a compressed archive) for Logos user and employee comments. The log files should provide more insight about open and crash (can compare content with logs from Logos 4.5b SR-1 on Mac OS X 10.6.8 that is working). From SQLite database file malformed error, suspect something needs deletion, possibly ~/Library/Application Support/Logos4/Documents/<random folder>/Documents/Clippings folder (could move Clippings folder to desktop, then try launching Logos 4 Mac).
Could enable diagnostic logging, restart Mac, launch Logos 4 Mac, click "Sign In" if dialog box appears. If Logos Bible Software 4 window does not appear, wait for 4 minutes. If still no window, then compress log files and attach to a forum reply. Wiki Mac Troubleshooting has => How to Report Bugs in Logos 4 Mac
Optional: download and use 5504.Logos4MacLogging.app.zip to display your logging setting, then change to enable logging.
Optional: download and use Logos Log Scribe application to create a zip file on your desktop that includes your diagnostic logs plus a copy of console messages.
Keep Smiling
I would follow smilings advise, but i had a very similar problem and it was fixed by going to your user Library folder, if using lion you can make it show up in the go menu by holding down the option key. Find the Updates.db file and remove it (note if this dose not solve the problem you might want to keep it to place it back, i will admit i was reckless and just deleted it, but just put it somewhere safe in case you want to put it back later). The possibly corrupt file is located here.
Invalid database: /Users/[YOURUSERNAME]/Library/Application Support/Logos4/Data/m7fvomqx.5xc/UpdateManager/Updates.db
I hope this helps you...
-dan
