Bug 1785917

Summary: KTouch is not compiled consistency with Qt
Product: [Fedora] Fedora Reporter: olibre
Component: ktouchAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 31CC: jreznik, kde-sig, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-22 23:26:41 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 olibre 2019-12-22 11:52:20 UTC 
Description of problem:

During installation of KTouch, GNOME-Software already warn an issue.

On start, KTouch says:

> **Typewriting Trainer has encountered a runtime error and has to be closed.**
>  
> qrc:/qml/main.qml: File was compiled ahead of time with an incompatible version of Qt and the original file cannot be found. Please recompile



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

    $ sudo dnf info ktouch
    Last metadata expiration check: 0:29:27 ago on Sun 22 Dec 2019 12:15:51 PM CET.
    Installed Packages
    Name         : ktouch
    Version      : 19.04.3
    Release      : 2.fc31
    Architecture : x86_64
    Size         : 9.1 M
    Source       : ktouch-19.04.3-2.fc31.src.rpm
    Repository   : @System
    From repo    : fedora
    Summary      : Touch Typing Tutor
    URL          : https://www.kde.org/applications/education/ktouch/
    License      : GPLv2+
    Description  : Touch Typing Tutor.



How reproducible:

Steps to Reproduce:
1. install
2. start



Actual results:

Does not start because KTuoch has not been well compiled.



Expected results:

Be compiled consistency with Qt.

 

Additional info:

nope
Comment 1 Rex Dieter 2019-12-22 23:26:41 UTC 

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