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:
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
I can confirm this bug as well. I can no longer launch nextcloud-client.
caused by recent abi-breaking re2 update, see also https://bugzilla.redhat.com/show_bug.cgi?id=1672014#c10
Should be fixed with latest rebuild, https://koji.fedoraproject.org/koji/buildinfo?buildID=1348834
(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?
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.
(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!
This is also happening in fc29, but `dnf distro-sync` does nothing
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.
Thanks Kevin, that fixed the problem for me.