Summary: | kbibtex for kde5 crashes at start in fc27 | ||
---|---|---|---|
Product: | [Applications] KBibTeX | Reporter: | Amaro <amaro> |
Component: | General | Assignee: | Thomas Fischer <fischer> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | rdieter |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | 1a360a63883b4b2cdac2f61912845c65c3a9c3bd | Version Fixed In: | 0.8 |
Sentry Crash Report: | |||
Attachments: | First check of qtoauth-qt5, only then for qtoauth |
Description
Amaro
2017-12-06 09:11:03 UTC
I cannot confirm this bug yet, but I may install Fedora in a virtual machine for further testing. (In reply to Amaro from comment #0) > Application: kbibtex (Git revision dabfd205 (master)) > > Qt Version: 5.9.2 > Frameworks Version: 5.40.0 > Operating System: Linux 4.13.16-302.fc27.x86_64 x86_64 > Distribution: "Fedora release 27 (Twenty Seven)" I set up a virtual machine with a fresh installation of Fedora 27, installing a Plasma desktop, and finally installing the necessary packages to compile and run KBibTeX. KBibTeX complied without errors, launching was successful as well. Qt Version: 5.9.2 Frameworks Version: 5.41.0 Linux kernel: 4.14.11-300.fc27.x86_64 Suggestions to continue from here: - Create a new user account on the same machine where you failed to run KBibTeX, try to compile and run KBibTeX there. - Setup a new Fedora 27 machine, either physically or virtual, try to compile and run KBibTeX there. If you succeed with either of above alternatives, try to narrow down the difference to the setup where running KBibTeX failed. The Fedora folks may be able to help you there. (In reply to Thomas Fischer from comment #2) > (In reply to Amaro from comment #0) > > Application: kbibtex (Git revision dabfd205 (master)) > > > > Qt Version: 5.9.2 > > Frameworks Version: 5.40.0 > > Operating System: Linux 4.13.16-302.fc27.x86_64 x86_64 > > Distribution: "Fedora release 27 (Twenty Seven)" > > I set up a virtual machine with a fresh installation of Fedora 27, > installing a Plasma desktop, and finally installing the necessary packages > to compile and run KBibTeX. > KBibTeX complied without errors, launching was successful as well. > > Qt Version: 5.9.2 > Frameworks Version: 5.41.0 > Linux kernel: 4.14.11-300.fc27.x86_64 > > Suggestions to continue from here: > - Create a new user account on the same machine where you failed to run > KBibTeX, try to compile and run KBibTeX there. > - Setup a new Fedora 27 machine, either physically or virtual, try to > compile and run KBibTeX there. > > If you succeed with either of above alternatives, try to narrow down the > difference to the setup where running KBibTeX failed. The Fedora folks may > be able to help you there. Hello Thanks for the help. I did try and create a new user and compile the master branch of kbibtex from git clone git://anongit.kde.org/kbibtex -b master then cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_BUILD_TYPE=debug ../kbibtex which outputs: -- Unity build disabled (default), use option UNITY_BUILD to enable it -- Found ICU 57.1.0 -- Found Qca-qt5 2.1.3 and QtOAuth -- Found both QtWebEngine and QtWebKit, preferring to use QtWebEngine -- The following OPTIONAL packages have been found: * Qt5Qml (required version >= 5.9.2) * Qt5Quick (required version >= 5.9.2) * Qt5WebChannel (required version >= 5.9.2) * Qt5Positioning (required version >= 5.9.2) * Qt5WebEngineCore (required version >= 5.9.2) * Qt5PrintSupport (required version >= 5.9.2) * Qt5WebEngineWidgets (required version >= 5.6.0) * Qt5WebKitWidgets (required version >= 5.6.0) * KF5DocTools * PkgConfig * Qca-qt5 (required version >= 2.1.0) * QtOAuth * SharedMimeInfo, A database of common MIME types, <http://freedesktop.org/wiki/Software/shared-mime-info/> -- The following REQUIRED packages have been found: * ECM (required version >= 5.19) * Qt5Core * Qt5Gui (required version >= 5.9.2) * Qt5Widgets * Qt5Network * Qt5XmlPatterns * Qt5 (required version >= 5.6.0) * Qt5Test (required version >= 5.6.0) * Gettext * PythonInterp * KF5I18n (required version >= 5.26.0) * KF5XmlGui (required version >= 5.26.0) * KF5KIO (required version >= 5.26.0) * KF5IconThemes (required version >= 5.26.0) * KF5ItemViews (required version >= 5.26.0) * KF5Completion (required version >= 5.26.0) * KF5Parts (required version >= 5.26.0) * KF5CoreAddons (required version >= 5.26.0) * KF5Service (required version >= 5.26.0) * KF5Wallet (required version >= 5.26.0) * KF5Crash (required version >= 5.26.0) * KF5 (required version >= 5.26.0) * Poppler, A PDF rendering library, <http://poppler.freedesktop.org> * ICU -- Configuring done CMake Warning (dev) in src/program/CMakeLists.txt: Policy CMP0071 is not set: Let AUTOMOC and AUTOUIC process GENERATED files. Run "cmake --help-policy CMP0071" for policy details. Use the cmake_policy command to set the policy and suppress this warning. For compatibility, CMake is excluding the GENERATED source file(s): "/home/amaro/Downloads/kbibtex-master/kbibtex/src/version.h" from processing by AUTOMOC. If any of the files should be processed, set CMP0071 to NEW. If any of the files should not be processed, explicitly exclude them by setting the source file property SKIP_AUTOMOC: set_property(SOURCE file.h PROPERTY SKIP_AUTOMOC ON) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) in src/parts/CMakeLists.txt: Policy CMP0071 is not set: Let AUTOMOC and AUTOUIC process GENERATED files. Run "cmake --help-policy CMP0071" for policy details. Use the cmake_policy command to set the policy and suppress this warning. For compatibility, CMake is excluding the GENERATED source file(s): "/home/amaro/Downloads/kbibtex-master/kbibtex/src/parts/version.h" from processing by AUTOMOC. If any of the files should be processed, set CMP0071 to NEW. If any of the files should not be processed, explicitly exclude them by setting the source file property SKIP_AUTOMOC: set_property(SOURCE file.h PROPERTY SKIP_AUTOMOC ON) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) in src/test/CMakeLists.txt: Policy CMP0071 is not set: Let AUTOMOC and AUTOUIC process GENERATED files. Run "cmake --help-policy CMP0071" for policy details. Use the cmake_policy command to set the policy and suppress this warning. For compatibility, CMake is excluding the GENERATED source file(s): "/home/amaro/Downloads/kbibtex-master/kbibtex/src/test/version.h" from processing by AUTOMOC. If any of the files should be processed, set CMP0071 to NEW. If any of the files should not be processed, explicitly exclude them by setting the source file property SKIP_AUTOMOC: set_property(SOURCE file.h PROPERTY SKIP_AUTOMOC ON) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) in src/test/CMakeLists.txt: Policy CMP0071 is not set: Let AUTOMOC and AUTOUIC process GENERATED files. Run "cmake --help-policy CMP0071" for policy details. Use the cmake_policy command to set the policy and suppress this warning. For compatibility, CMake is excluding the GENERATED source file(s): "/home/amaro/Downloads/kbibtex-master/kbibtex/src/test/version.h" from processing by AUTOMOC. If any of the files should be processed, set CMP0071 to NEW. If any of the files should not be processed, explicitly exclude them by setting the source file property SKIP_AUTOMOC: set_property(SOURCE file.h PROPERTY SKIP_AUTOMOC ON) This warning is for project developers. Use -Wno-dev to suppress it. -- Generating done -- Build files have been written to: /home/amaro/Downloads/kbibtex-master/kbibtex then sudo make install The same error occurs as before, and kbibtex crashes at the start. Best regards Amaro Hello Figured it out. Had to remove the optional packages qoauth and qoauth-devel 2.0.0-4.fc27, recompiled kbibtex for kf5 and it works. Minor aspect is that installation creates a non-standard /usr/lib64/plugins directory solely for kbibtexpart.so even though all other plugins for qt5 are in /usr/lib64/qt5/plugins, had to create a symbolic link there. Thanks. Amaro Created attachment 109863 [details]
First check of qtoauth-qt5, only then for qtoauth
It may be an issue that during configuration (cmake phase), KBibTeX is configured to look for the 'qtoauth' library instead of 'qtoauth-qt5'.
For some Linux distributions like Gentoo, 'qtoauth' is the Qt5 variant and there is no Qt4 variant. For other distributions like Fedora, there exists both a 'qtoauth' variant (Qt4) and a 'qtoauth-qt5' variant (Qt5). Just checking for 'qtoauth' as done without this patch may work in Gentoo but fail on Fedora as it will try to make use of a Qt4-based library in a Qt5-based program (at least, this is the working thesis).
(In reply to Amaro from comment #4) > Figured it out. Had to remove the optional packages qoauth and qoauth-devel > 2.0.0-4.fc27, recompiled kbibtex for kf5 and it works. You comment pointed me to a potential issue due to the different names of the Qt5-based QtOAuth library on Gentoo Linux and Fedora. Please see attachment 109863 [details] for details. Before testing this patch, please install qoauth-qt5-devel and dependencies. > Minor aspect is that > installation creates a non-standard /usr/lib64/plugins directory solely for > kbibtexpart.so even though all other plugins for qt5 are in > /usr/lib64/qt5/plugins, had to create a symbolic link there. The install path for the parts plugin comes from the variable KDE_INSTALL_PLUGINDIR which is use even in core KDE apps like Dolphin's part. I assume that official Fedora packages for KDE redefine KDE_INSTALL_PLUGINDIR to point to /usr/lib64/qt5/plugins, whereas the default is /usr/lib64/plugins. Simply try to set the environment variable KDE_INSTALL_PLUGINDIR=/usr/lib64/qt5/plugins before running cmake and make. Hello Thomas Thanks for the patch, it worked and compiled well with qoauth-qt5-devel and cmake -DKDE_INSTALL_QTPLUGINDIR:PATH=`qtpaths --plugin-dir` -DCMAKE_INSTALL_PREFIX:PATH=`kf5-config --prefix` -DCMAKE_BUILD_TYPE=debug ../kbibtex Best regards Amaro Message for commit 1a360a63883b4b2cdac2f61912845c65c3a9c3bd that fixed this bug was not automatically processed thus not closing this bug; doing it manually now. |