BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1397/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Mon, 14 Feb 2022 01:40:38 +
Build duration:
11 min and counting
JUnit Tests
Name: projectroot Fa
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1380/
Project:
kf5-qt5 SUSEQt5.15
Date of build:
Mon, 14 Feb 2022 01:40:38 +
Build duration:
10 min and counting
BUILD ARTIFACTS
acc/KF5KIO-5.91.0.xml
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20FreeBSDQt5.15/402/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Mon, 14 Feb 2022 00:40:42 +
Build duration:
1 min 45 sec and counting
JUnit Tests
Name: p
On Sonntag, 13. Februar 2022 19:27:22 CET alexander.loh...@gmx.de wrote:
> Hello,
>
> Usually the KCMs are opened by starting kcmshell or systemsettings with the
> module names as arguments,
> meaning we resolve the location of the KCMs internally and don't require
> changes for consumers. kcms
Hello,
Usually the KCMs are opened by starting kcmshell or systemsettings with the module names as arguments,
meaning we resolve the location of the KCMs internally and don't require changes for consumers. kcmshell also checks if the plugin id
would match if the "kcm_" prefix is to the modul
On Sonntag, 13. Februar 2022 14:15:09 CET Fusion Future wrote:
> On 2022/2/13 20:20, Martin Koller wrote:
> > I already tried this but it did not solve the issue.
>
> This code snippet works on my system. Please have a try.
>
> ```cpp
> dialog = new KCMultiDialog();
>
> KPluginMetaData
> module
On Sonntag, 13. Februar 2022 04:59:51 CET Fusion Future wrote:
> On 2022/2/13 05:46, Martin Koller wrote:
> > What has changed and how would I now use the new KCM in a KCMultiDialog ?
>
> It can be changed to "kcm_bluetooth". Please see [1] to see if that helps.
>
> [1] https://invent.kde.org/pla
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/369/
Project:
kf5-qt5 SUSEQt5.15
Date of build:
Sun, 13 Feb 2022 15:33:37 +
Build duration:
4 min 15 sec and counting
JUnit Tests
Name:
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.15/368/
Project:
kf5-qt5 SUSEQt5.15
Date of build:
Sun, 13 Feb 2022 15:29:12 +
Build duration:
4 min 25 sec and counting
JUnit Tests
Name:
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20FreeBSDQt5.15/323/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Sun, 13 Feb 2022 15:29:12 +
Build duration:
2 min 31 sec and counting
JUnit Tests
On 2022/2/13 21:31, Martin Koller wrote:
But still I wonder if such a change is something like breaking ABI
compatibility.
If KDE/plamsa is such a moving target where I can not rely on compatibility even
between minor versions, that is really not fun.
Perhaps the breakage is due to these comm
On 2022/2/13 20:20, Martin Koller wrote:
I already tried this but it did not solve the issue.
This code snippet works on my system. Please have a try.
```cpp
dialog = new KCMultiDialog();
KPluginMetaData
module(QPluginLoader("plasma/kcms/systemsettings/kcm_bluetooth"));
if (!module.name().i
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20SUSEQt5.15/1379/
Project:
kf5-qt5 SUSEQt5.15
Date of build:
Sun, 13 Feb 2022 09:57:24 +
Build duration:
14 min and counting
BUILD ARTIFACTS
acc/KF5KIO-5.91.0.xml
BUILD UNSTABLE
Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1396/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Sun, 13 Feb 2022 09:57:25 +
Build duration:
6 min 22 sec and counting
JUnit Tests
Name: projectr
14 matches
Mail list logo
