Bug 1739232

Summary:	symbol lookup error: /lib64/libQt5WebEngineCore.so.5: undefined symbol: _ZN3re23RE23Arg9parse_intEPKciPv
Product:	[Fedora] Fedora	Reporter:	Cristiano Furtado <cristianofurtadoba>
Component:	qt5-qtwebengine	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	goanrauk, kde-sig, kevin, leandroembu, nonamedotc, rdieter, thomas
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:	2019-08-12 13:54:57 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:
Bug Depends On:
Bug Blocks:	1738594

Description Cristiano Furtado 2019-08-08 19:43:34 UTC

Description of problem:
not working

Version-Release number of selected component (if applicable):
ksysguard-5.16.4-1.fc31.x86_64

How reproducible:
undefined symbol: _ZN3re23RE23Arg9parse_intEPKciPv

Steps to Reproduce:
1. open konsole
2. ksysguard
3.

Actual results:
ksysguard: symbol lookup error: /lib64/libQt5WebEngineCore.so.5: undefined symbol: _ZN3re23RE23Arg9parse_intEPKciPv

Expected results:


Additional info:

Comment 1 Leandro Ramos 2019-08-08 19:50:24 UTC

I confirm this bug:

Steps to Reproduce:
1. open konsole
2. ksysguard
3.

Actual results:
ksysguard: symbol lookup error: /lib64/libQt5WebEngineCore.so.5: undefined symbol: _ZN3re23RE23Arg9parse_intEPKciPv

Comment 2 Mukundan Ragavan 2019-08-08 22:08:39 UTC

I can confirm this bug as well. I can no longer launch nextcloud-client.

Comment 3 Rex Dieter 2019-08-09 19:52:24 UTC

caused by recent abi-breaking re2 update, see also
https://bugzilla.redhat.com/show_bug.cgi?id=1672014#c10

Comment 4 Rex Dieter 2019-08-12 13:54:57 UTC

Should be fixed with latest rebuild,

https://koji.fedoraproject.org/koji/buildinfo?buildID=1348834

Comment 5 Mukundan Ragavan 2019-08-12 21:03:02 UTC

(In reply to Rex Dieter from comment #4)
> Should be fixed with latest rebuild,
> 
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1348834

this is happening in F30 as well. Can this be pushed to F30?

Comment 6 Rex Dieter 2019-08-12 21:08:46 UTC

The re2 f30 update was withdrawn,
https://bodhi.fedoraproject.org/updates/FEDORA-2019-a49097c021

you'll need to downgrade.

dnf distro-sync
should do that for you.

Comment 7 Mukundan Ragavan 2019-08-12 21:29:56 UTC

(In reply to Rex Dieter from comment #6)
> The re2 f30 update was withdrawn,
> https://bodhi.fedoraproject.org/updates/FEDORA-2019-a49097c021
> 
> you'll need to downgrade.
> 
> dnf distro-sync
> should do that for you.

Thank you!

Comment 8 goanrauk 2019-08-15 05:56:31 UTC

This is also happening in fc29, but `dnf distro-sync` does nothing

Comment 9 Kevin Kofler 2019-08-15 09:59:00 UTC

See bug #1741108. The broken re2 update made it out to the Fedora 29 stable updates due to a bug in the update system (Bodhi). Another update (https://bodhi.fedoraproject.org/updates/FEDORA-2019-605dfb7384) was filed to revert re2 to a known good version, but has not reached updates-testing yet. The immediate workaround for Fedora 29 is:

sudo dnf --disablerepo=updates --disablerepo=updates-testing distro-sync re2
(WARNING: Do not forget to specify "re2" in that distro-sync line or you will end up downgrading everything to non-updated Fedora 29!)

and then --exclude=re2 on all further updates until bug #1741108 is fixed. See https://bugzilla.redhat.com/show_bug.cgi?id=1741108#c5 for an explanation.

Comment 10 goanrauk 2019-08-16 05:15:29 UTC

Thanks Kevin, that fixed the problem for me.