Update ready to be installed Issue

Each time I start Logos 6, I receive the message that an update is ready to install...do I want to update (recommended). If I say yes, then a new message tells me another Logos setup is already in progress...please wait for it to finish.

This has happened for a few days now. The only way to start Logos 6 is to respond to the update with a no. Then the program opens.

I am thus currently running

Logos Bible Software 6.0a
6.0.1.0032

Log is attached

Find more posts tagged with

Comments

Mark

The content of the log:

[1204/202630:ERROR:renderer_main.cc(227)] Running without renderer sandbox

What does this mean?

Mark

https://community.logos.com/discussion/comment/671182#Comment_671182

The program no longer showed this morning the update message. It did update today. But the log still says:

[1205/075953:ERROR:renderer_main.cc(227)] Running without renderer sandbox

Can anyone tell me what this means and how to fix it?

Dave Hooton

https://community.logos.com/discussion/comment/671350#Comment_671350

The program no longer showed this morning the update message. It did update today. But the log still says:

[1205/075953:ERROR:renderer_main.cc(227)] Running without renderer sandbox

Can anyone tell me what this means and how to fix it?

CEF stands for Chromium Embedded Framework. It is the embedded web browser technology that powers features like the new homepage, ...so this is not the diagnostic log from the Logos software (see https://wiki.logos.com/Diagnostic_Logging) and the 'renderer' message can be safely ignored.

Post future software issues in the Logos 6 forum where it will be acknowledged more quickly.

Mark

https://community.logos.com/discussion/comment/671492#Comment_671492

Thanks Dave

the CEF file is the only file in my Logos Log file (besides the enablelogging script). I have opened and closed L6 many times. You can still see that this is the file that is generated. If I delete the file, then it will be recreated when reopening Logos. The attached CEF file actually mentions Logos. No other file appears in the log file.

I have been to the wiki page. Before I posted this thread I went there to enable logging. As I mentioned above, this is the only file that appears.8053.cef.log

Dave Hooton

https://community.logos.com/discussion/comment/671651#Comment_671651

If I delete the file, then it will be recreated when reopening Logos. The attached CEF file actually mentions Logos. No other file appears in the log file.

It is unusual as you would normally have LogosError.log which is also produced automatically. When you enable logging you should see Logos.log and LogosIndexer.log. These three are produced by the Logos software. CEF is not Logos software as it is third party.

Mark

https://community.logos.com/discussion/comment/672242#Comment_672242

Well, whether I use the enable logging script or disable logging script, always when I open Logos 6, I get only one file, this CEF file. If I delete it and try again with logging enabled or disabled, this file still shows up in the Logos Log File folder.

So now I closed Logos 6 again, deleted this CEF file so the folder is clear, and restarted Logos 6 using the temporary method of holding down the control key. This time, I get 3 files showing in the folder, one is still the CEF file. All 3 files are attached.

0815.LogosIndexer.log

5224.Logos.log

4150.cef.log

If the CEF file is 3rd party, is there some way to get it off my computer? Why would it be appearing each time I open Logos 6 and is it dangerous?

Chaoyu-Bian

https://community.logos.com/discussion/comment/672268#Comment_672268

Well, whether I use the enable logging script or disable logging script, always when I open Logos 6, I get only one file, this CEF file. If I delete it and try again with logging enabled or disabled, this file still shows up in the Logos Log File folder.

So now I closed Logos 6 again, deleted this CEF file so the folder is clear, and restarted Logos 6 using the temporary method of holding down the control key. This time, I get 3 files showing in the folder, one is still the CEF file. All 3 files are attached.

0815.LogosIndexer.log

5224.Logos.log

4150.cef.log

If the CEF file is 3rd party, is there some way to get it off my computer? Why would it be appearing each time I open Logos 6 and is it dangerous?

same problem here.[:'(]

Dave Hooton

https://community.logos.com/discussion/comment/672268#Comment_672268

All 3 files are attached.

Delete the folders \Logos5\Data\2ruxd5bv.5ed\DownloadManager\ and

\Logos5\Data\2ruxd5bv.5ed\ResourceManager\Downloaded and

restart Logos.

Dave Hooton

https://community.logos.com/discussion/comment/672268#Comment_672268

If the CEF file is 3rd party, is there some way to get it off my computer?

CEF is third party as is SQLite and they are used/needed by Logos to perform specific functions. Both produce logs or log messages for diagnostic purposes, but the CEF.log is not as important as the specific Logos logs.

Dave Hooton

https://community.logos.com/discussion/comment/672283#Comment_672283

same problem here.

Please provide logs as per https://wiki.logos.com/Diagnostic_Logging.

Mark

https://community.logos.com/discussion/comment/672367#Comment_672367

All 3 files are attached.

Delete the folders \Logos5\Data\2ruxd5bv.5ed\DownloadManager\ and

\Logos5\Data\2ruxd5bv.5ed\ResourceManager\Downloaded and

restart Logos.

Not sure what this does, but I deleted them, restarted Logos and have attached logs. I guess all is okay. Appreciate the help.

8875.LogosIndexer.log

8371.Logos.log

5545.cef.log

Question that may be helpful to put on the wiki: If one has a diagnostic problem, is there a quick solution such as deleting certain folders and restarting logos that may help 50% of the time? In other words, are there folders that can be deleted without harming anything, that will reappear on a restart of Logos and that often solves many diagnostic problems?

Dave, again, your help has always been appreciated. Thanks again.

Dave Hooton

https://community.logos.com/discussion/comment/672398#Comment_672398

Not sure what this does, but I deleted them, restarted Logos and have attached logs.

To prevent the Indexer being called for bogus updates, delete the folder

\Logos5\Data\2ruxd5bv.5ed\UpdateManager\ and restart Logos to restore it.

If one has a diagnostic problem, is there a quick solution such as deleting certain folders and restarting logos that may help 50% of the time? In other words, are there folders that can be deleted without harming anything, that will reappear on a restart of Logos and that often solves many diagnostic problems?

For resource update issues you could try deleting the UpdateManager and DownloadManager folders I've shown you, but rename the Downloaded folder in case it has updates that matter. Without logs there is no quick solution for other issues.

Mark

https://community.logos.com/discussion/comment/672570#Comment_672570

Thanks again, Dave. It was very difficult to delete a logos installer that was in the updatemanager folder. Even after restarting the computer twice and using an unlock program, it would not delete. But it finally deleted on the 3rd restart of the computer. All looks good now. That installer is no longer in the updatemanager folder.

Chaoyu-Bian

https://community.logos.com/discussion/comment/672369#Comment_672369

same problem here.

Please provide logs as per https://wiki.logos.com/Diagnostic_Logging.

attached here:

3872.EnableLogging.zip

Dave Hooton

https://community.logos.com/discussion/comment/672825#Comment_672825

attached here:

The only issue from the logs is a Warning "UserManager Couldn't unprotect user's string: Key not valid for use in specified state".
To fix it you can try to uninstall a Windows Update KB2918614 but you should contact Faithlife Tech Support if it does not work.

Dave Hooton

https://community.logos.com/discussion/comment/673242#Comment_673242

Chaoyu-Bian

Is your issue fixed?