Description of problem: After updating osinfo-db to version osinfo-db-20180318-1.fc27.noarch Google Chrome has been logged out. Chrome version is 65.0.3325.181 (Official Build) (64-bit). Seems that some information has been erased or renamed so Chrome cannot reach it anymore. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
To the best of my knowledge there is absolutely no relationship between osinfo-db and Google Chrome. osinfo-db is used only be virtualization mgmt tools, and is not relevant to execution of web browsers. Furthermore, the osinfo-db RPM merely contains static XML files, no functional content, so shouldn't be able to break any app. Can you provide more info about why you think osinfo-db impacted Chrome ? It feels like mere co-incidental timing to me.
(In reply to Daniel Berrange from comment #1) > To the best of my knowledge there is absolutely no relationship between > osinfo-db and Google Chrome. osinfo-db is used only be virtualization mgmt > tools, and is not relevant to execution of web browsers. Furthermore, the > osinfo-db RPM merely contains static XML files, no functional content, so > shouldn't be able to break any app. > > Can you provide more info about why you think osinfo-db impacted Chrome ? > It feels like mere co-incidental timing to me. Thank you for the reply. I assume osinfo-db changed something in the environment because the only package that was updated after the previous usage of Google Chrome is osinfo-db. May be it was coincidential. I don't have arguments against anymore, and we just have to wait until someone else faces this problem.
If you can find any info that shows osinfo-db as a cause, then feel free to re-open.