Bug 1741316

Summary: anki crashes on startup
Product: [Fedora] Fedora Reporter: Andras Simon <szajmi>
Component: ankiAssignee: Thomas Drake-Brockman <thomas>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 29CC: chkr, david, 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-25 08:41:26 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: 1741108    
Bug Blocks:    

Description Andras Simon 2019-08-14 18:26:21 UTC
Description of problem:

anki crashes on startup

Version-Release number of selected component (if applicable):

anki-2.1.14-1.fc29.noarch

How reproducible:

Easily.

Steps to Reproduce:
1. start anki from the command line
2.
3.

Actual results:

[simon@localhost tmp]$ anki 
Traceback (most recent call last):
  File "/usr/bin/anki", line 6, in <module>
    import aqt
  File "/usr/share/anki/aqt/__init__.py", line 14, in <module>
    from aqt.qt import *
  File "/usr/share/anki/aqt/qt.py", line 17, in <module>
    from PyQt5.QtWebEngineWidgets import *
ImportError: /lib64/libQt5WebEngineCore.so.5: undefined symbol: _ZN3re23RE23Arg9parse_intEPKciPv


Expected results:

anki starting normally

Additional info:

It worked before today's batch of upgrades, which are

Upgrading:
 LibRaw               x86_64      0.19.4-1.fc29          updates      302 k
 libmodulemd1         x86_64      1.8.15-3.fc29.1        updates      162 k
 postgresql-jdbc      noarch      42.2.6-1.fc29          updates      713 k
 re2                  x86_64      20190801-1.fc29        updates      175 k

Comment 1 david 2019-08-15 22:13:28 UTC
Downgrading re2 to 20160401-7.fc29 is a viable workaround until it's fixed.

Comment 2 Christian Krause 2019-08-15 22:48:22 UTC
A bug report [1] was already created for re2 and an update is currently already in submitted [2]. So the issue should be solved in a about a week when the update to re2 is officially available. 

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1741108
[2] https://bodhi.fedoraproject.org/updates/FEDORA-2019-605dfb7384

Comment 3 Andras Simon 2019-08-16 12:03:58 UTC
(In reply to david from comment #1)
> Downgrading re2 to 20160401-7.fc29 is a viable workaround until it's fixed.

Thanks!

Comment 4 Christian Krause 2019-08-25 08:41:26 UTC
Since the update to re2 was released 
https://bodhi.fedoraproject.org/updates/FEDORA-2019-605dfb7384
I'm closing this bug report as duplicate #1741108.

*** This bug has been marked as a duplicate of bug 1741108 ***