-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plasma 6 support? #42
Comments
Heyho, I have a local KF6 port. I will look into making the project compile/work with both Plasma5 and Plasma6 |
it was more work to get it done properly, but I have pushed a first version. I will need to look at some test failures and check some Qt6 deprecation messages. |
to try it out, run cmake with the -DBUILD_WITH_QT6=ON option set. I have updated the install script to better search for the plugin path so that it should be picked up. I will resume tomorrow :) |
I tried with |
Have you started with a clean build? Maybe you can attach the cmake log (I have build it with self compiled Qt and KDE Frameworks) |
Yeah, I have built from scratch, with the PKGBUILD that I did not yet published: this one. I am currently using Plasma 6 beta 2 from kde-unstable repo in Arch Linux. After installing a built package, I run Also, in .install file I guess it should be
What exact file should I search for? |
-DKDE_INSTALL_QTPLUGINDIR= That looks incorrect |
Can you please suggest what is should be? I do not have the |
Please see 708b703 |
Thanks. I now used this line for cmake command (edited the gist at the link above):
Then I did |
Can you try enabling debug logs for krunner and the kcoreaddons core lib? You could utilize the kdebugsettings utility. The install manifest would be useful too. Pa: killall fails afaik when there is no process running. Might that cause issues? |
No. I did it manually, and before that, I checked that
First of all, thanks for your support! After I hit Ok button, the KDebugSettings closes (I see the exit status 1 in the terminal), and the next time I open it, it still has previous values. I guess that is not normal?
The contents of
|
What would be interesting is if The paths from the install manifest show up in the kcoreaddons debug logs. Usually they say in which dirs were searched for plugins. Maybe an ls in /usr/lib/qt/plugins/kf6/krunner/ can help too? Just to verify that this is where the other kde plugins are installed too |
There is only that file that is installed with package that I built. I did not installed any other runners manually. |
I have both |
No, when plasmashell and the krunner executable come from Plasma6, that should be fine.
qdbus org.kde.krunner /MainApplication org.qtproject.Qt.QApplication.aboutQt When I enable the mentioned logging categories, I get output like kf.coreaddons: Checking for plugins in QList("/home/user/kde/usr/bin/kf6/krunner", "/home/user/kde/usr/plugins/kf6/krunner") Maybe you can try getting the logs using the ENV var: And what does |
Thanks. Yes, in that window I see it is written "This program uses Qt version 6.7.0".
Yes, I was able to see logs that way. I also added ";default=false" to the QT_LOGGING_RULES.
But the package have them in different path:
Note there the path is not /usr/lib/qt6.
|
if(KDE_INSTALL_USE_QT_SYS_PATHS)
# Qt-specific vars
ecm_query_qt(qt_plugins_dir QT_INSTALL_PLUGINS)
if(_qt_prefix_is_cmake_install_prefix)
file(RELATIVE_PATH qt_plugins_dir ${qt_install_prefix_dir} ${qt_plugins_dir})
endif()
_define_absolute(QTPLUGINDIR ${qt_plugins_dir} "Qt plugins")
ecm_query_qt(qt_qml_dir QT_INSTALL_QML)
if(_qt_prefix_is_cmake_install_prefix)
file(RELATIVE_PATH qt_qml_dir ${qt_install_prefix_dir} ${qt_qml_dir})
endif()
_define_absolute(QMLDIR ${qt_qml_dir} "QtQuick2 imports")
else() Maybe we run into issues because of this behavior in ECM. Can you try without the /usr install prefix? |
And please check if you have the qtpaths file somewhere else on disk. Or maybe a package is missing, though I'd not expect such issues from Arch where they are not mentally split into pices. |
Removing
|
And what does the /usr/lib/qt6/bin/qtpaths6 executable give you for the plugin path? And you have that installed, or was it only a search for the package manager? |
How can I check that?
The first command (pkgfile) searches in the official packages (that may not be installed). |
Your normal qtpaths is a Qt5 bases one? That should output a Qt5 specific dir when |
if(NOT QUERY_EXECUTABLE)
if(ARGS_TRY)
set(${result_variable} "" PARENT_SCOPE)
message(STATUS "No ${_exec_name_text} executable found. Can't check ${qt_variable}")
return()
else()
message(FATAL_ERROR "No ${_exec_name_text} executable found. Can't check ${qt_variable} as required")
endif()
endif() Maybe the QUERY_EXECUTABLE is not found and thus it silently fails -_- Can you try editing /usr/share/ECM/modules/ECMQueryQt.cmake and add a warning before the check I posted? |
|
And the ECM stuff I mentioned in my second comment? |
It gives the following message:
|
Hmm, but that looks like the correct executable which previously yielded the correct path. Or do you somehow get the message multiple times? Maybe you could add log statements to /usr/share/ECM/kde-modules/KDEInstallDirs6.cmake:219 and print what is done in CMake here |
Yeah, I am getting those messages several times. The full output of the cmake command:
Something like adding |
Yeah, trace sounds good. Or adding more warnings ;) PS: Happy new Year! |
This is the cmake line in PKGBUILD (
Here is the output: makepkg with traced cmake 20240101.txt Happy New Year! |
Oh man, this is such a confusing topic... Try changing the few lines from 222 onward (KDEInstallDirs6) message(WARNING "qt_plugins_dir: ${qt_plugins_dir}, prefix dir of Qt ${qt_install_prefix_dir}")
if(_qt_prefix_is_cmake_install_prefix)
file(RELATIVE_PATH qt_plugins_dir ${qt_install_prefix_dir} ${qt_plugins_dir})
endif()
_define_absolute(QTPLUGINDIR ${qt_plugins_dir} "Qt plugins")
message(WARNING "qtpluginsdir is now: ${qt_plugins_dir} after resolving relative KDE_INSTALL_QTPLUGINDIR: ${KDE_INSTALL_QTPLUGINDIR}") /usr/share/ECM/modules/ECMQueryQt.cmake(96): set(${result_variable} ${output_path} PARENT_SCOPE ) The "QTPLUGINDIR lib/qt6/plugins Qt plugins" line looks suspicious, the qt_plugins_dir variable we got shouldn't contain a space. |
I added the warnings to lines 222 and 227 in KDEInstallDirs6, and the output is:
I also uncommented |
But |
Oh, sorry, looks like I accidently did not saved the |
This is super weird, I can't find anything wrong in the cmake logs. My suggestion would be to use qtpaths to pass in the plugin dir explicitly. Please also file a bug on bugs.kde.org and link to this issue. Maybe someone with arch system packages has more luck hunting down this bug. What also seems off to me is that according to the trace, we run the first time in the if-block for the cache. I wish I could come up with a more proper solutions :( |
I have filed a bug 479941. I have tried to manually move the |
I now tried to remove both pkg and src directories (actually, build with makepkg after cloning the aur pkgbuild), and it seems it helped. It now have built with the correct path. |
Great! So we may consider this issue resolved? |
Yes. Just add the new aur package to readme. |
Done! |
I've managed to install the plugin on kde6 with fedora 39 (nobara) downloading the install.sh and modifying the cmake line: cmake -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF -DBUILD_WITH_QT6=ON -DCMAKE_POSITION_INDEPENDENT_CODE=ON .. --trace Also is needed to have the qt dependencies installed: sudo dnf install kf6-kdoctools-debuginfo-6.0.0-1.fc39.x86_64 kf6-ki18n-debuginfo-6.0.0-1.fc39.x86_64 kf6-kservice-devel-6.0.0-1.fc39.x86_64 kf6-krunner-devel-6.0.0-1.fc39.x86_64 kf6-ktextwidgets-devel-6.0.0-1.fc39.x86_64 kf6-kio-devel-6.0.0-1.fc39.x86_64 kf6-kcmutils-devel-6.0.0-1.fc39.x86_64 |
This is a GCC issue. I fixed it in the jetbrains-api submodule @Ashark I have made some changes and published a 2.0.0 release. Old manual mappings will be discarded, but it is more reliable/performant/simple now :) |
@alex1701c Thanks for notification. I have updated it. Is this part still correct in the install script?
I just updated my package, and it did not (currently) have any post-install scripts with such instruction. Also, in readme in this line:
you can remove Plasma 5, as it is no longer exists. |
Hello.
Can I use these plugins in Plasma 6? I tried installing with "Get New Stuff", but it gave error.
If that can be used in Plasma 6, can you please update the building instructions? Then I will upload a
plasma6-runners-jetbrains-runner-git
to aur.The text was updated successfully, but these errors were encountered: