BUG: 4.0c Beta 2 - Maybe
I noticed that each time I start L4 the Logos icon appears in the system tray with the indexing library message calculating time remaining. After a couple of seconds it goes away and the program starts normally. I did not notice this happening with Beta 1 and it does not happen with the stable release 4.0b on my netbook. Not sure if this is a bug or not.
Comments
-
Fred Chapman said:
I noticed that each time I start L4 the Logos icon appears in the system tray with the indexing library message calculating time remaining. After a couple of seconds it goes away and the program starts normally. I did not notice this happening with Beta 1 and it does not happen with the stable release 4.0b on my netbook. Not sure if this is a bug or not.
I get this too. Just now it showed up for about three seconds and then went away before L4 was even fully loaded.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I noticed this too. The tray icon appeared in previous versions. But the system tray balloon tips seem more prevalent now, appearing when they didn't use to.
MacBook Pro (2019), ThinkPad E540
0 -
The indexer is started by L4 when it detects something needs to be fixed or attended to eg. update in progress, keylink manager needs updating, resources need discovery.
This morning L4 decides "the bible index needs to be updated" and starts the Indexer. The Indexer goes to Stage 3, starts calculating time remaining, decides 1 resources in the Bible index need updating but concludes that the bible Index is actually OK and stops after 1.5 sec!
This has happened before (spurious indexing) in Beta 1 and 4.0b.
Dave
===Windows 11 & Android 13
0 -
Fred Chapman said:
I noticed that each time I start L4 the Logos icon appears in the system tray with the indexing library message calculating time remaining. After a couple of seconds it goes away and the program starts normally. I did not notice this happening with Beta 1 and it does not happen with the stable release 4.0b on my netbook. Not sure if this is a bug or not.
I've noticed this in 4.0c beta 1 and 2. It never seems to do anything and never gets to a calculated time, but does stick around long enough to produce a balloon. Seems to slow things down. Lasts longer than you have it - up to 2 minutes while Logos opens and populates my home page.
Annoying.
0 -
Everybody attach your indexer logs so a pattern can be demonstrated.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Everybody attach your indexer logs so a pattern can be demonstrated.
Attached is my Index log
I am far from an expert at reading these things, but it appears that the indexer is going through a house cleaning process every time the program starts. I don't know if this is good or bad. I guess I would rather have it spend a few seconds doing this than crashing. Like I said in the previous post, it does not seem to impact the functionality of the program once everything is started.
0 -
Here's mine,
The only thing displayed besides info messages is one warning:
Warn ResourceManager Resource of type SyntaxDatabase could not be found at location C:\Users\Rich\AppData\Local\Logos4\Data\2e2k45uv.psv\ResourceManager\Resources\LexhamSGGNT.lbssyn with ID DB:SYNTAX-LEXHAMSGGNT and version 2009-10-06T03:08:43Z
I'm also uploading my Logos log, as it shows a few warnings as well.
It also shows the indexer process first as not running (08:57:29.1150), and then it looks like it creates the Bible index at 08:57:29.1631. Then it finds the index, then creates it and launches the indexer process at 08:57:29.1771 "because the Bible index needs to be updated. Then at 08:57.32.7742 it creates the library index in much (but not quite) the same way, as no indexer process is launched.
Hope this helps track down the issue.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:
Then at 08:57.32.7742 it creates the library index in much (but not quite) the same way, as no indexer process is launched.
The log time is 08:57:32.7343 and completed in 3ms. Note that the library index's libraryindex.db file is discovered but further action is not necessary unlike the bible index's libraryindex.db earlier. The weird thing is that the Indexer processes the bible index command by 08:57:32.6753 and L4 says it is complete at 08:57:32.3322 but the Indexer then resumes at 08:58:20.2140 (a gap of about 47sec!) and checks the Library Index!
What happened in that "gap"? Why did L4 think the Indexer had finished at 08:57:32.3322?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Everybody attach your indexer logs so a pattern can be demonstrated.
Sorry, I've been out of "Forum Land" for a while. Here's my logs from this morning.
0 -
Hi Chris
Your log shows the ignored bug of L4 trying to update obsolete resources.
First delete LexhamSGGNT.lbssyn and LexhamSGGNT.lbxclv together with LexSGGlossary.logos4 from the L4 resource folder (if present).
They are in your hidden \Logos4 folder. Go to Control Panel | Folder Options to view them.
Then I'd like you to delete:-
- any files in \ResourceManager\Downloaded
- \DownloadManager\DownloadManager.db
- \UpdateManager\Updates.db
- any resources in \UpdateManager\Resources
Finally start L4 and post both Logos4 log files to the forum.
Dave
===Windows 11 & Android 13
0
