BUG or Setting??
Open Logos, Open 'Bible Books Explorer', 'All' Bible books selected (no filter) [although filtered down to a sub topic/area doesn't matter], Select 'Intertext', Select any Bible book at perimeter for Scripture references (either OT or NT book), Search panel lists duplicate Scripture references under 'Passages' or 'Aligned'.
BTW - Selecting 'Grid' crashes Logos. Requires restart of application.
Is this a bug or do I need to change a setting to eliminate the duplicate listings?
Comments
-
Hi Michael - and welcome to the forums
Open Logos, Open 'Bible Books Explorer', 'All' Bible books selected (no filter) [although filtered down to a sub topic/area doesn't matter], Select 'Intertext', Select any Bible book at perimeter for Scripture references (either OT or NT book), Search panel lists duplicate Scripture references under 'Passages' or 'Aligned'.
I'm not seeing this - as below
What platform are you running Logos on - and which version of Logos do you have?
Can you post a screenshot showing what you describe? Please use the paperclip icon in the forum editor to upload the screenshot in a reply to this thread.
BTW - Selecting 'Grid' crashes Logos. Requires restart of application.
I have seen this on Mac (and reported it) - are you running on that platform?
Graham
0 -
-
Interesting...
I just reselected other-than NASB95 as favorite and the duplications don't exist. Tried NIV, ESV, NASB2020 and NKJV all appear OK. Looks to be an issue with NASB95
0 -
-
I am running Windows 11, Logos Bible Study 29.1, 29.1.22
i notice that you have these Search options enabled (shaded):
They should not affect the result, but what happens if they are deselected and what bibles are selected in Multi-book View?
You should get 66 results with NASB95, so try reindex nasb95 in the Command Box as re-indexing might fix it.
Dave
===Windows 11 & Android 13
0 -
Hi Michael--Really sorry for the trouble on this.
We saw something similar with another user (for context: https://community.logos.com/forums/t/218656.aspx); in his case, he somehow got some bibles in his "personal book index" (and those same bibles were in his LibraryIndex--where they should be); the presence in both indices is what was causing the duplicate results (and by the way, the Grid view crash is almost certainly also due to the duplicate results, which grid view never expects).
So let's see if the personal book index is also your issue.
First, close the application completely.
Next, you'll want to find your personal book index files. On Windows, I believe these should be located at `C:/Users/{your username}/AppData/Local/Logos4/Data/{some random folder name}/PersonalBookIndex`.
You'll end up blowing away this entire folder, but if you don't mind, it might be helpful for us to get our hands on your `LibraryIndex.db` file from inside the `PersonalBookIndex` folder (the file may just be labeled `LibraryIndex` in file explorer). Could you upload that here to this thread?
After uploading that file, delete the entire `PersonalBookIndex` folder.
After deleting that folder, restart the application (the index will be re-created by the application automatically, but hopefully without putting the NASB95 in the index), and check whether or not you're still getting duplicated results for that resource. Let us know either way.
Hope it solves your problem...we're still digging into how the personal book index might be getting into this state. Let us know if you can think of anything unique you may have done before you started seeing this issue. But anyway, it seems to be rare, so hopefully if deleting the index will solve things for you.
0 -
Hi Ronny (and others who posted suggested steps to solve the issue)!!
Sorry for the tardiness in reply but was out of town and just back to try these various steps. Info as follows:
1. Graham: I did re-add my NASB95 bible to my favorites and forced a reindex as you noted. Same operation as before - no change to results, still offered duplicates.
2. Dave: I did de-select those additional search criteria, re-indexed NASB95 and repeated the same operation as before - no change to results, still offered duplicates.
3. Ronny - Attached is the LibraryIndex.db file. I deleted that host folder (PersonalBookIndex) and restarted the application. I then repeated the same operation as before and this time, the results only returned the single (not duplicated) Scripture references! Yay!! Hope the attached .db file provides some insight on the issue. Thanks again for your help.
0 -
Thanks for the update, and for posting the LibraryIndex.db file.
We have learned that the reindex command actually precipitates the duplicate search results bug (it will incorrectly also index the resource in the personal book index.) We are working on a fix, but in the mean time if anyone needs to use the reindex command you would also need to follow it up by running the Rebuild personal book index command.
There are 294 other indexed resources in that LibraryIndex.db file besides NASB95 though. I'm assuming you didn't run the reindex command on all of those! We are investigating that aspect as well.
0 -
but in the mean time if anyone needs to use the reindex command you would also need to follow it up by running the Rebuild personal book index command.
There are issues not resolved by a Rebuild, although my PB index only includes PBB's:-
2023-12-08 11:12:28.6852 INFO 10 IndexerProgram | (Timed) Updating Personal Book Index from Resource Manager.
2023-12-08 11:12:28.6856 INFO 10 PersonalBookIndex | Full re-index (and deletion of existing index) requested.
2023-12-08 11:12:28.6904 INFO 10 PersonalBookIndex | Checking 3275 resources that may have changed since they were last indexed.
2023-12-08 11:12:28.6983 WARN 10 PersonalBookIndex | Resource 'PBB:53a2a90052aa4a4d9b5cf7eeead99399' could not be opened.
2023-12-08 11:12:28.6989 WARN 10 PersonalBookIndex | Resource 'PBB:32b99f5066f8443d804535e2d5bda96d' could not be opened.
2023-12-08 11:12:28.7939 WARN 10 PersonalBookIndex | Resource 'PBB:8a240040f07040ffb39abf1a97214670' could not be opened.
2023-12-08 11:12:28.7956 WARN 10 PersonalBookIndex | Resource 'PBB:6f032aefbf9f40f3a3147e8b0ae3bf5c' could not be opened.
2023-12-08 11:12:28.7962 WARN 10 PersonalBookIndex | Resource 'PBB:b1015e596bb7498d970544130aa17267' could not be opened.
2023-12-08 11:12:28.7980 WARN 10 PersonalBookIndex | Resource 'PBB:d56d43875af9497b9f46cf4b4ef97fdd' could not be opened.
2023-12-08 11:12:28.7987 WARN 10 PersonalBookIndex | Resource 'PBB:03b08b42b7f84cf8909f60379e6328e9' could not be opened.
2023-12-08 11:12:28.8116 INFO 10 PersonalBookIndex | 7 resources need to be indexed, and will be merged into an index of 11 resources.
2023-12-08 11:12:28.8126 INFO 10 PersonalBookIndex | Final count: 18 resources need to be indexed; no merge necessary.
2023-12-08 11:12:28.8130 INFO 10 IndexerProgram | (128ms) Updating Personal Book Index from Resource Manager.
2023-12-08 11:12:28.8189 INFO 10 IndexerProgram | (Timed) Indexing.
2023-12-08 11:12:28.8190 INFO 1 WindowsIndexerProgram | Setting notification icon tool tip to: Verbum is indexing (0% complete)
2023-12-08 11:12:28.8213 INFO 10 IndexerProgram | Waiting for library indexing to finish.
2023-12-08 11:12:28.8232 INFO 16 LibraryIndex | 0 unindexed resources out of 2795 indexable resources; supplemental index count is 0.
2023-12-08 11:12:28.8236 INFO 16 LibraryIndex | All indexable resources are indexed in a single main index; marking index up-to-date.
2023-12-08 11:12:28.8266 INFO 17 PersonalBookIndex | 0 unindexed resources out of 18 indexable resources; supplemental index count is 0.Consider:
- "7 resources need to be indexed, and will be merged into an index of 11 resources"
- "Final count: 18 resources need to be indexed; no merge necessary."
- "0 unindexed resources out of 18 indexable resources;".
All these statements are incorrect, arising from 7 PBB's that could not be opened from the 'IndexedResources' table of 18 PBB's. 11 is the correct number of indexable resources, and these were duly indexed. Only the 'Resources' table correctly recognises the 11 PBB that are Indexed (Status 3).
Deleting the PB Index folder is a more robust way to correct any errors (IMHO).
Dave
===Windows 11 & Android 13
0 -
There are issues not resolved by a Rebuild
I don't think those are issues from the application's viewpoint, but that being said,
Deleting the PB Index folder is a more robust way to correct any errors (IMHO).
That will work equally well
0