[resolved] Since when does Logos require restarting Chrome to reinstall? Grrrrr!

I thought Logos had moved away from dependencies on browsers as of L4. Now we're back with interconnections with a browser? I find it very annoying to be forced to restart Chrome when installing an update to Logos. I'm in the middle of several things in several tabs right now. Fortunately, Chrome does a pretty good job of saving my place, even partially filled in forms usually, but I still don't want to have to shut it down and risk losing certain info (it doesn't do it perfectly).

Note that I was running Logos 6.3 Beta 1 before this update came along, and I'm still running Logos 6.3 Beta 1 after, so it must have been an update of only Logos Prerequisites.

Find more posts tagged with

Comments

MJ. Smith

When log files include a CEF file and the copyright stuff includes

Chromium Embedded Framework

I think we can be certain the Faithlife is using a Chrome module but not Chrome per se.

Rosie Perera

https://community.logos.com/discussion/comment/717984#Comment_717984

Yes, but why should Faithlife be saving a new version of that Chrome module over my existing one? Without updating Chrome too, it might destabilize things. And if they are not actually updating the version of that module which Chrome uses, then why do I have to restart Chrome?

Incidentally, I refused to restart Chrome and so far don't seem to be having any problems, but if the message is not required, it's too bad it has to come up. Maybe Logos doesn't have any control over it and Chrome does that.

Graham Criddle

Also discussed at https://community.logos.com/forums/t/103698.aspx - interesting that it seems to affect Firefox as well.

NB.Mick

https://community.logos.com/discussion/comment/717993#Comment_717993

Incidentally, I refused to restart Chrome and so far don't seem to be having any problems, but if the message is not required, it's too bad it has to come up.

I did the same, but later on in the install had to restart Windows - not sure if that's related.

Rosie Perera

https://community.logos.com/discussion/comment/717995#Comment_717995

I did the same, but later on in the install had to restart Windows - not sure if that's related.

I also refused to restart Windows, and both Logos and Chrome are running fine.

Dave Hooton

Note that I was running Logos 6.3 Beta 1 before this update came along, and I'm still running Logos 6.3 Beta 1 after, so it must have been an update of only Logos Prerequisites.

Logos Prerequisites is apparently deprecated and it was removed from my installation, to the detriment of my stable version. So it seems likely that a shared dependency on browser modules was being removed.

Mark Barnes

https://community.logos.com/discussion/comment/718014#Comment_718014

I doubt very much that there's any dependices on browsers. It's much more likely that Chrome and Logos share a common dependency which needed to be upgraded/removed by the pre-requisites.

Mark Barnes

https://community.logos.com/discussion/comment/718014#Comment_718014

Logos Prerequisites is apparently deprecated and it was removed from my installation, to the detriment of my stable version.

I think you misunderstood Bradley's post. He was simply saying that the requirements had changed between 6.2 and 6.3, so 6.2 requisites were no longer needed, but 6.3 requisites still are needed.

Dave Hooton

https://community.logos.com/discussion/comment/718018#Comment_718018

I think you misunderstood Bradley's post

I was referring to the removal of Logos Prerequisites from Control Panel >> Programs and Features (the deprecated quote comes from the 6.3 Update script and log).

Undoubtedly there are 6.3 prerequisites but I'm not sure about its mechanism.

Dave Hooton

https://community.logos.com/discussion/comment/718017#Comment_718017

It's much more likely that Chrome and Logos share a common dependency which needed to be upgraded/removed by the pre-requisites.

Wasn't that what I said!?

Mark Barnes

https://community.logos.com/discussion/comment/718194#Comment_718194

It's much more likely that Chrome and Logos share a common dependency which needed to be upgraded/removed by the pre-requisites.

Wasn't that what I said!?

You and Rosie were both talking about dependency on browser modules, not sharing a common dependency with browsers. Perhaps I over-exegeted the preposition!

Rosie Perera

https://community.logos.com/discussion/comment/718244#Comment_718244

It's much more likely that Chrome and Logos share a common dependency which needed to be upgraded/removed by the pre-requisites.

Wasn't that what I said!?

You and Rosie were both talking about dependency on browser modules, not sharing a common dependency with browsers. Perhaps I over-exegeted the preposition!

Yes, we were talking about Logos sharing a common dependency with the Chrome browser. But the thing that both Logos and the browser are dependent on is a module that was created by the Chrome folks. That's the Chromium Embedded Framework, technology that Logos incorporated into version 6. Calling it a "browser module" might have been slightly unclear on Dave's part. But I knew what he meant. He didn't mean a part of the browser, but rather a module that the browser is built on top of.

Anyway, it's all pretty fuzzy where you draw the line between what is a part of some software and what is merely something that the software depends on.

Mark Barnes

https://community.logos.com/discussion/comment/718253#Comment_718253

But the thing that both Logos and the browser are dependent on is a module that was created by the Chrome folks. That's the Chromium Embedded Framework, technology that Logos incorporated into version 6. Calling it a "browser module" might have been slightly unclear on Dave's part.

I'm pretty sure that's not the case. (That is, I'm pretty sure that CEF is not causing the problem, as that's entirely independent of Chrome, and it's not installed as part of the pre-requisites, it's just bundled with the Logos desktop app.)

I think that what's happened is that Logos 6.2 installed the Visual C++ 2013 Runtime, which 6.3 doesn't — possibly because of this change: https://msdn.microsoft.com/en-us/library/windows/hardware/dn448963%28v=vs.85%29.aspx. 6.3 therefore uninstalls the runtime (or more accurately it uninstalls 6.2s prerequisites), and it's that which causes Chrome to want to close.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/718256#Comment_718256

I'm pretty sure that's not the case. (That is, I'm pretty sure that CEF is not causing the problem, as that's entirely independent of Chrome, and it's not installed as part of the pre-requisites, it's just bundled with the Logos desktop app.)

Mark is correct.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/718342#Comment_718342

FWIW I just installed 6.3 RC2 on my home machine (while Chrome was running) and there was no prompt to close Chrome or any other browser.

Rosie Perera

https://community.logos.com/discussion/comment/726287#Comment_726287

Good to hear it.