4.53.0.2264 4.5b SR-3 2012 May 29 Tue 4.52.0.2208 4.5b SR-2 2012 May 17 Thu 4.52.0.2202 4.5b SR-1 2012 May 8 Tue 4.52.0.2194 4.5b RC 2 “Gold” 2012 May 1 Tue 4.52.0.2176 4.5a SR-1 2012 Mar 15 Thu 4.51.0.2057 – New resources only for Logos 4 4.5a RC 2 “Gold” 2012 Feb 23 Thu 4.51.0.2048 – also included Beta channel 4.5 SR-5 2012 Feb 8 Wed 4.50.0.1893 4.5 SR-4 2012 Feb 1 Wed 4.50.0.1889 4.5 SR-3 2012 Jan 31 Thu 4.50.0.1881 4.5 SR-2 2012 Jan 26 Thu 4.50.0.1869 4.5 SR-1 2012 Jan 25 Wed 4.50.0.1860 4.5 RC 3 “Gold” 2012 Jan 24 Tue 4.50.0.1857 – also included Beta channel 4.3 SR-8 2011 Dec 28 Wed 4.30.0.1624 4.3 SR-7 2011 Dec 5 Mon 4.30.0.1621 4.3 SR-6 2011 Oct 25 Tue 4.30.0.1613 4.3 SR-5 2011 Oct 4 Tue 4.30.0.1603 4.3 SR-4 2011 Sep 28 Wed 4.30.0.1597 – also included Beta channel 4.3 SR-3 2011 Sep 12 Mon 4.30.0.1592 4.3 SR-2 2011 Aug 24 Wed 4.30.0.1572 4.3 SR-1 2011 Aug 16 Tue 4.30.0.1553 4.3 RC 3 “Gold” 2011 Aug 9 Tue Mac 4.30.0.1517; Win 4.30.0.1516 – Diagnostic

4.50.0.1275 4.5 Beta 3 2011 Oct 20 Thu 4.50.0.1189 4.5 Beta 2 2011 Oct 13 Thu 4.50.0.1145 4.5 Beta 1 2011 Oct 12 Wed 4.50.0.1142 – Warning: if change update channel to Beta, can change to Stable after 4.5 stable release 4.3 Release Candidate 3 2011 Aug 3 Wed Mac 4.30.0.1517; Win 4.30.0.1516 – 4.3 “Gold” Stable release 4.3 Release Candidate 2 2011 Aug 2 Tue 4.30.0.1512 4.3 Release Candidate 1 2011 Jul 28 Thu Mac 4.30.0.1497; Win 4.30.0.1498 4.3 Beta 13 2011 Jul 20 Wed 4.30.0.1437 – OS X 10.7 Lion officially released earlier on same day 4.3 Beta 12 2011 Jul 12 Tue 4.30.0.1276 – OS X 10.7 Lion compatible 4.3 Beta 11 2011 Jul 5 Tue Mac 4.30.0.1146; Win 4.30.0.1145 4.3 Beta 10 2011 Jun 28 Tue Mac 4.30.0.1045; Win 4.30.0.1046 4.3 Beta 9 2011 Jun 21 Tue 4.30.0.0964 4.3 Beta 8 2011 Jun 14 Tue 4.30.0.0882 4.3 Beta 7 2011 Jun 7 Tue Mac 4.30.0.0802; Win 4.30.0.0803 4.3 Beta 6 2011 May 31 Tue 4.30.0.0735 4.3 Beta 5 2011 May 17 Tue Mac 4.30.0.0586; Win 4.30.0.0587 – Diagnostic

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Logos can crash without generating a log file.

Diagnostic Logs Logs record the activity of the software in a way that assists identification of the feature or module that is causing a problem.

Diagnostic Logging Wiki: TOC, VTOC, Home Forum: Home, General See also  Uploading Logs  Bug Report  Screenshot  Logos Help Center  Report a Problem A diagnostic log is a detailed report of what the Logos program is doing and it is used to diagnose problems.

Logos 28.0 RC 1 Version: 28.0.32 Release Date: September 5, 2023 Bug Fixes Reporting Improved logging for crash reports.

To log into the forum you use the same User Id and Password that you use to log into the Logos site.

.), then we usually want to see some logs from the desktop and mobile applications before we can help.

Faithlife Status – Check server issue(s), or follow @FaithlifeDevOps Using the Forums for friendly discussions about Faithlife stuff LBS Platform Feature Comparison: Desktop, Mobile, Web Blogs & News – General Interest & Products by Faithlife Corporation Contact – Faithlife email addresses & phone numbers FAQ : Faithlife, Ebooks, Logos, Verbum, Notes, Connect, Privacy Policy, Faithlife Study Bible, Faithlife TV, Lexham Press, Terms of Service Faithlife Feedback – Help Prioritize Development : Announcement Desktop App Issues Logos Support (LS) + Verbum Support (VS) LS Desktop + VS Desktop LS Support FAQ + VS Support FAQ LS Free Support + VS Free Support LS Optimizing + VS Optimizing LS Remote Assistance LS Report a Problem – PC & Mac VS Report a Problem – Mac VS Report a Problem – PC LS Installing + VS Installing Installing & Indexing Questions – PC & Mac Diagnostic Logging – PC & Mac Screenshot – PC & Mac Windows Screen Reader – PC Windows Troubleshooting

The deleted files will be listed in the Logos.log if Diagnostic Logging is active.

Logos Help Center (LHC) includes What to do if Logos crashes & How-to-Enable-and-Submit-Log-Files with macOS Logging selection box.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Option: can open diagnostic log to verify scan path added: Logos Application Diagnostic Log Logos /Users/username/Library/Application Support/Logos4/Logging/Logos.log Verbum /Users/username/Library/Application Support/Verbum/Logging/Verbum.log After scan path command is entered, scanning begins immediately.

Logos Help Center (LHC) includes What to do if Logos crashes & How-to-Enable-and-Submit-Log-Files with macOS Logging selection box.

Uploading Logs Wiki: TOC, VTOC, Home Forum: Home, General When you’ve completed your Bug Report in the Forums, you need to attach a copy of the Logs that were indicated by the wiki article Diagnostic Logging.

These documents were compiled as personal books, and a further script examined the warning logs generated by Logos to determine which verses are unsupported by each datatype.

You should also provide log files from your attempt to start Logos.

How do I upload log files to the Logos Forums?  

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

If they are authorized to connect to the document (either because it’s shared to “All Users” and they’re logged in, or because it’s shared to a Faithlife group that they are connected to) they will see a blue “Actions” button in the upper right, where they can choose to connect to the document.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Page Contents Where do I find the Warning/Error log?

Diagnostic logging was enabled until Logos 4.3 Beta 5 (version 4.30.0.0586), when default was changed to improve performance, Logos Logging application can show then optionally change diagnostic logging, refer to Mac Diagnostic Logging for details Enable Mac Diagnostic Logging (always includes indexer logging) Repeat buggy issue OR crash (unexpected disappearance) in Logos 4 Mac Immediately after Logos 4 Mac issue repeats OR crashes (and before relaunching), open a Finder window, press Command-Shift-G, and enter “~/Library/Application Support/Logos4” (without the quotation marks) in sheet that pops up, then press OK.

Mac and PC User Interface Differences Wiki: TOC, VTOC, Home Forum: Home, General See also  Keyboard Shortcuts For Mac  Keyboard Shortcuts For Windows  Logos 4 Mac  Mac Release Notes and History Page Contents Common Experience Default File Path Easter Egg – Mac only Feature Parity – Mac needs some improvements Floating Window Indexer Icon Keyboard Shortcuts Logging Microsoft Word Hyperlinks Morphology Pop-up Notes Spell Check Printing & Export Program Icon Program Scaling Resource Update Right Click Search – Handouts Screen layout File Guides Layouts Tools Common Experience Logos for Mac and Logos for PC share code base – most items function identically on both platforms (including right and left mouse click options in File, Guides, and Layouts menus).

Thus, while it remains possible to install and run Libronix on a Windows desktop, this installation can no longer connect to Libronix servers to sychronize your licenses) Associate License Online Log into Logos.com OR forums OR Faithlife with your Faithlife account Use https://www.logos.com/Redeem Enter your product key (OR serial #) Call Customer Service You call 1 (800) 875-6467 (US), 0871-218-1700 (UK) Sample Conversation ring, ring Receptionist: Logos Bible Software, how may I direct your call?

Include your Logos.log and LogosError.log files.

Forum link: http://community.logos.com/forums/ Status: invalid – Log files or crash dump are needed (post on forum or with tech support staff).

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

Reporting Problems You should have logging permanently enabled because you will be expected to upload logs for diagnostic purposes to the Logos Desktop Beta forum , especially after a crash.

If a reference cell cannot be parsed, the software will skip that field, and leave a warning message in the log.

Logos 9.3 RC 1 Version: 9.3.0.0039 Released: February 23, 2021 New Features My Library Added some additional logging.

Android Reader 8.12.2.0031 Fixed - Fixed potential Notes sync issue - Prevent attempted use of Notes when not logged in

- Fixed Biblia Text Comparison crash when user is not logged in.

- Fixed Biblia Text Comparison crash when user is not logged in.

Android Reader 8.8.0.0021 Improved - Potential crash log improvement Fixed - Various bug fixes

(Bob Pritchett, CEO) Log in security and the lack of multiple user accounts under Logos (Bob Pritchett, CEO) Security and Privacy (Bob Pritchett, CEO) Logos Security (Bob Pritchett, CEO) Preventing Sync Data Loss (Bob Pritchett, CEO) What Logos does when it installs and what log files are (Bryan Albert) Messing with resource files discouraged (Bob Pritchett, CEO) Retagging resources as the Logos catalog expands (Bob Pritchett, CEO) What happens to typo reports?

Logging Moved the default logging folder location to: %LocalAppData%\Faithlife\Logs\Logos\ %LocalAppData%\Faithlife\Logs\Verbum\ Bug Fixes Canvas Fixed a bug that prevented Word Info Cards from showing up.

New Features for Windows Logging Moved the default logging folder location to: %LocalAppData%\Faithlife\Logs\Logos\ %LocalAppData%\Faithlife\Logs\Verbum\ Changes Search Removed the “Search (while typing)” option from Bible Search.

Logging Added new logging to track when resources are removed.

Logging Added new logging to track when resources are removed, this is cumulative rather than for each session.

Sign-In Updated the log-in screen brand icons.

Improvements Sign-In Updated the log-in screen brand icons.

If Controlled Folder Access is turned on Logos Logs will now be saved in %LOCALAPPDATA%\Logos\Logos Log Files and %LOCALAPPDATA%\Logos Log Files.

If Controlled Folder Access is turned on Logos Logs will now be saved in %LOCALAPPDATA%\Logos\Logos Log Files and %LOCALAPPDATA%\Logos Log Files.

Thread Startup Fixed bug where Work Offline option was missing when logging in.

Faithlife Assistant Commands Calendar Based Tasks General Navigation Help Bible Navigation Resource Navigation Narration Search Definition & Lookup Documents Guides Tools Bible Browser Trivia Settings Account & Orders Diagnostic & Maintenance He is risen!

Improvements Performance Modified ngen to hide the process log and launch Logos.

If you experience any issues, please post your logs and any reproduction steps in the Logos Desktop Beta Forum.

If you have any unexpected behavior with startup or indexing, please inform us on the forums and post logs if available.

Logos Windows Profiler Utility Important Note This is not a “general purpose” diagnostic tool.

Additional logging to help with future issue reports

Android Reader 5.12.4 Build 117 Fixed Added back crash logging

How do I enable diagnostic logging?

How do I enable diagnostic logging?

Fixed The Verse of the Day is now properly localized (in the Biblia app) Internal crash log report fixes

Updater Fixed a patching error when downloading new resources and updating existing resources resulting in “Catastrophic failure” in the log.

Updater Fixed a patching error when downloading new resources and updating existing resources resulting in “Catastrophic failure” in the log.

Please post your Logos.log file on the Thread and then run Repair in Programs and Features.

Android Reader 4.6.4 Improved Improved crash logging and reporting

iOS Reader 4.6.4 New Improved logging for “Report a Problem” Smarter loading of text range note attachments Fixed Opening Note Documents should no longer crash the app Deleting History items should no longer crash the app

Logos Fixed numerous crashes in various areas in the application that had been reported by our automatic crash logging.

Logos Fixed numerous crashes in various areas in the application that had been reported by our automatic crash logging.

Personal Book Builder Fixed crash when building Personal Book if the Logging folder didn’t have read/write/execute permissions correctly set.

Fixed crash when building books caused by the Logos\Logging\PBB\Logs folder becoming unwriteable.

Fixed crash when building books caused by the Logos\Logging\PBB\Logs folder becoming unwriteable.

Creating a Hang Dump The instructions are the same as above, except in step 2, run Logos4: procdump -h -x "%LOCALAPPDATA%\Logos4\System\Logos4.exe" Logos4.dmp Logos5: procdump -h -x "%LOCALAPPDATA%\Logos5\System\Logos.exe" Logos5.dmp Collecting Diagnostics for the Indexer If the Logos 4 Indexer is hanging or crashing, use the same instructions as above, but change Logos4.exe in the commands to Logos4Indexer.exe

Logging    “Unparsed reference: popup.pos” errors are no longer appearing in the Logos.log file.

LLS Resources    “Unparsed reference: popup.pos” errors are no longer appearing in the Logos.log file.

Synchronization    Attempting to sync after changing password while logged in will provide a message prompting a restart and re-login.

Startup Fixed bug which could occur when logging in with incorrect credentials.

Startup Fixed crash which could occur when logging in with incorrect credentials.

Personal Book Builder Fixed bug which caused error in log file when input text box was created.

If possible please follow the directions for Diagnostic Logging and Uploading Logs to include a diagnostic log with your post.

Note that the expiration of your certificates might have been caused by you changing the date/time on your machine. 3) Proxy server problems This is one more possible obscure cause (Windows): Check the log file for an error like this: “The remote server returned an error: (514) Web Acceleration Client Error (514) – Proxied HTTPS Request Not Supported.”

The application is not ready until after the user has logged in successfully, the main window has appeared, and any startup operations have completed.

If you crash on startup, hold down ‘control’ when you startup the program and make offline selection in order to run the program in diagnostic mode and then remove NRSV bible from the Preferred Bible list on the Homepage.

Log In Screen Fixed bug which prevented the “Why?”

Bug Fixes for Windows Setup Fixed bug which prevented installing Logos without being logged into Windows as the administrative user.

Log In Screen Fixed bug which prevented the “Why?”

Known Issues Synchronization Some users may see a yellow “sync error” icon and have the following text logged in Logos4Error.log (see this thread): Request: GET https://librarycatalogapi.logos.com/collections/v1/sync (status InternalServerError

SQLite errors are logged to the application error log.

Social Sharing Clicking the Faithlife icon in the info pane for Bibles will display a web page with a runtime error if Faithlife.com is not already logged into a user account.

SQLite errors are logged to the application error log.

New Features for Mac Logging Implemented creation of Logos4Error.log file when errors occur, even if logging isn’t enabled (this matches an existing Windows feature.)

New Features for Mac Logging Implemented creation of Logos4Error.log file when errors occur, even if logging isn’t enabled (this matches an existing Windows feature.)

Entering this command will download all of the sync items on the server and compare them to the sync items on the client, reporting any mismatches to the Logos4.log (if logging is enabled) as well as to a new “Logos4Error.log.”

Added a ‘View log file...’ link to panel post-compilation for easy access to Personal Book log files.

Diagnostic Logging Full Logging has been disabled to improve performance in the program.

With log file attached... =========== Thanks guys.

SEE lastest post for the lates log file (only produces one file) and screen shots.

Here’s what I did to cause Logos to abnormally terminate and capture log file: a.

Forum link: http://community.logos.com/forums/ Status: invalid If indexer crash has not been resolved, please provide logs or contact Customer Support.

Forum link: http://community.logos.com/forums/ Status: invalid If problem is not resolved, please provide logs, or contact Technical Support at tech@logos.com.

Diagnostic Logging Full Logging has been disabled to improve performance in the program.

It appears that resource id’s are case sensitive as the logs state:-        ‘LLS:gs_jbmw_10’ is out of date        ‘LLS:GS_JBMW_10’ is up to date Software version: 4.0a.

Comments Log files (attached) indicate that the cause of the crash was Error Program Unhandled exception: Libronix.DigitalLibrary.Logos.IndexingException: No translation word for specified document position —> System.ArgumentException: No translation word for specified document position    at Libronix.DigitalLibrary.Resources.ReverseInterlinear.ReverseInterlinearResourceCore.GetTextAlignment(IWorkState state, Int32 nStartDocumentPosition, Int32 nEndDocumentPosition)    at Libronix.DigitalLibrary.Resources.ReverseInterlinear.ReverseInterlinearResource.GetTextAlignment(IWorkState state, Int32 nStartDocumentPosition, Int32 nEndDocumentPosition)    at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.ProcessReverseInterlinearIndexData(NativeLogosResourceIndexer* pNativeIndexer, Char* pszSourceId, ReverseInterlinearColumnIndexData* pData, Int32 nDataCount)    at Libronix.DigitalLibrary.Logos.Callback.ProcessReverseInterlinearIndexData(Callback* , NativeLogosResourceIndexer* pNativeIndexer

Bug: Logos 4 Perpetually indexing when Windows 7 starts The Logos 4 indexer starts every time I log into Windows or re-start Windows; however, it appear that the indexing is not actually working because my search function does not work properly.