Description of problem: Qt Creator help is broken/missing. Version-Release number of selected component (if applicable): qt-creator-3.0.1-4.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. yum install qt-creator 2. qtcreator 3. Choose Help/Contents from the menu Actual results: Error 404... The page could not be found! Error loading: qthelp://org.qt-project.qtcreator.301/doc/index.html Expected results: A helpful Qt Creator Manual opens. Additional info: What is missing seems to be /usr/share/doc/qtcreator/qtcreator.qch. With that in place, the help starts to work.
/usr/share/doc/qt-creator/qtcreator*.qch should be moved to /usr/share/doc/qt5, so that qt-creator can auto-detect them.
Testing on Rawhide, if I do Help -> Contents, I get the Qt Creator Manual displayed as I would expect, and is correctly listed in the Contents tree. What is broken in your view?
I am on Fedora 26 with qt-creator-4.2.2-3.fc26.x86_64. Can you check the actual path of qt-creator qch in Rawhide qt-creator?
$ dnf repoquery -l qt-creator-doc.noarch /usr/share/doc/qtcreator /usr/share/doc/qtcreator/qtcreator-dev.qch /usr/share/doc/qtcreator/qtcreator.qch
Oh boy, someone "fixed" the docs on F26... http://pkgs.fedoraproject.org/cgit/rpms/qt-creator.git/commit/?h=f26&id=251e4e56c3df51683b80f4accd999c45b1a615f8
Fix building: https://koji.fedoraproject.org/koji/buildinfo?buildID=918576
fixed and built for f26: https://koji.fedoraproject.org/koji/taskinfo?taskID=20521899
qt-creator-4.2.2-5.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-0e2aafb9c7
qt-creator-4.2.2-5.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-0e2aafb9c7
qt-creator-4.2.2-5.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.