On 29.08.20 00:54, Ben Cooksley wrote:
On Sat, Aug 29, 2020 at 10:49 AM Nicolas Fella mailto:nicolas.fe...@gmx.de>> wrote:
On 29.08.20 00:34, Ben Cooksley wrote:
On Sat, Aug 29, 2020 at 8:02 AM Nicolas Fella
mailto:nicolas.fe...@gmx.de>> wrote:
Hi Ben,
Hi Nicolas,
On Sat, Aug 29, 2020 at 10:49 AM Nicolas Fella wrote:
> On 29.08.20 00:34, Ben Cooksley wrote:
>
> On Sat, Aug 29, 2020 at 8:02 AM Nicolas Fella
> wrote:
>
>> Hi Ben,
>>
>
> Hi Nicolas,
>
>
>>
>> the only place where I'm aware that qmlplugin is used in KDE Connect is
>> ecm_find_qmlmodule. Using
On 29.08.20 00:34, Ben Cooksley wrote:
On Sat, Aug 29, 2020 at 8:02 AM Nicolas Fella mailto:nicolas.fe...@gmx.de>> wrote:
Hi Ben,
Hi Nicolas,
the only place where I'm aware that qmlplugin is used in KDE
Connect is
ecm_find_qmlmodule. Using qmlplugindump on the relevant modul
On Sat, Aug 29, 2020 at 8:02 AM Nicolas Fella wrote:
> Hi Ben,
>
Hi Nicolas,
>
> the only place where I'm aware that qmlplugin is used in KDE Connect is
> ecm_find_qmlmodule. Using qmlplugindump on the relevant modules works
> fine on my Linux machine though and I'm not aware of recent changes
Hi Ben,
the only place where I'm aware that qmlplugin is used in KDE Connect is
ecm_find_qmlmodule. Using qmlplugindump on the relevant modules works
fine on my Linux machine though and I'm not aware of recent changes that
might cause this. I however do not have access to a Windows machine at
thi
Hi all,
It appears that at some point in recent history something in KDE
Connect has changed, which now causes it's build to hang on the Binary
Factory until the hanging process (qmlplugindump) is manually
terminated.
The affected log can be found at
https://binary-factory.kde.org/job/kdeconnect-