Bug 1560934

Summary:	Google Chrome logged out after osinfo-db update
Product:	[Fedora] Fedora	Reporter:	Vlad <vinogradov.vlad.a>
Component:	osinfo-db	Assignee:	Daniel Berrangé <berrange>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	27	CC:	berrange, fidencio, vinogradov.vlad.a
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-28 09:09:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vlad 2018-03-27 09:46:54 UTC

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:

Comment 1 Daniel Berrangé 2018-03-27 10:24:36 UTC

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.

Comment 2 Vlad 2018-03-27 22:36:04 UTC

(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.

Comment 3 Daniel Berrangé 2018-03-28 09:09:00 UTC

If you can find any info that shows osinfo-db as a cause, then feel free to re-open.