KDE Connect doesn't work with latest KF5 at all. In systray settings there is no option to enable kde connect at all. Running kdeconnect-cli ends up with the error: > kdeconnect-cli -l \kdeconnect-cli(20425)/kdeconnect DevicesModel::refreshDeviceList: dbus interface not valid 0 devices found Reproducible: Always
(In reply to Vit Pelcak from comment #0) > KDE Connect doesn't work with latest KF5 at all. In systray settings there > is no option to enable kde connect at all. > > Running kdeconnect-cli ends up with the error: > > > kdeconnect-cli -l > \kdeconnect-cli(20425)/kdeconnect DevicesModel::refreshDeviceList: dbus > interface not valid > 0 devices found > > Reproducible: Always Same problem here with debian testing and plasma 5
It looks like the daemon is not running, so the CLI tool can't connect to it. That's pretty strange, since the daemon is DBus-activated, which means that whenever another app tries to use it through dbus it should launch the process on the fly. Does it work if you first run the daemon directly (usually from /usr/lib/libexec/kdeconnectd)? Also, can you make sure that the dbus-activation file (should be in /usr/share/dbus-1/services/org.kde.kdeconnect.service) points to the correct daemon executable path? Thanks!
Hi Albert, The daemon is properly set at /usr/lib/kde4/libexec/kdeconnect in the dbus-activation file, and once the daemon is launched manually i am not receiving any more the error saying interface not present, but i still miss the icon in the tray and the plasmoid, the only way of interacting so far is command-line. Any guess?? Thanks.
Hello. It is absolutely the same for me. Only that path differs a bit a I'm on openSUSE.
Hello, I have upgraded to sid and now i cant even start the daemon at startup, this is the bug report that i have recolect. I hope it can help. Application: kdeconnectd (0.1) KDE Platform Version: 4.14.13 Qt Version: 4.8.7 Operating System: Linux 4.2.0-1-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: <En detalle, comente que estaba haciendo cuando la aplicación se cerró.> The crash can be reproduced every time. -- Backtrace: Application: kdeconnect (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7febf2868900 (LWP 1108))] Thread 3 (Thread 0x7febdf2aa700 (LWP 1135)): #0 0x00007febef7415fd in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007febecd6a4d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007febecd26cc4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007febecd27180 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007febecd272ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007febf045e406 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007febf042c331 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007febf042c6a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007febf031b579 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007febf031de6c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007febed20e0a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x00007febef74e06d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7febd7fff700 (LWP 1452)): #0 0x00007febf045de2a in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #1 0x00007febecd2676d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007febecd2710b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007febecd272ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007febf045e406 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007febf042c331 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007febf042c6a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007febf031b579 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007febf040c393 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007febf031de6c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007febed20e0a4 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x00007febef74e06d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7febf2868900 (LWP 1108)): [KCrash Handler] #6 0x00007febee98b172 in QCA::PrivateKey::decrypt(QCA::SecureArray const&, QCA::SecureArray*, QCA::EncryptionAlgorithm) () from /usr/lib/x86_64-linux-gnu/libqca.so.2 #7 0x00007febf251682e in NetworkPackage::decrypt(QCA::PrivateKey&, NetworkPackage*) const () from /usr/lib/libkdeconnectcore.so.1 #8 0x00007febf250dd04 in ?? () from /usr/lib/libkdeconnectcore.so.1 #9 0x00007febf04421c0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007febf250f566 in ?? () from /usr/lib/libkdeconnectcore.so.1 #11 0x00007febf04421c0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x00007febeecdd5fe in ?? () from /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 #13 0x00007febeece646d in ?? () from /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 #14 0x00007febf132f8dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #15 0x00007febf1336816 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #16 0x00007febf20b172a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #17 0x00007febf042dabd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x00007febf045e9b2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #19 0x00007febecd26fe7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007febecd27240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007febecd272ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x00007febf045e406 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #23 0x00007febf13d9a36 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #24 0x00007febf042c331 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x00007febf042c6a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #26 0x00007febf0432689 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #27 0x00000000004011d0 in ?? () #28 0x00007febef689b45 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #29 0x0000000000401237 in _start () Report to https://bugs.kde.org/
That stack trace looks like your private key got corrupted. Can you try deleting your kdeconnect config files, to see if that recovers from the problem? They should be in ~/.kde4/share/apps/kdeconnect and ~/.kde4/share/config/kdeconnectrc (even though it might be slightly different depending on your distro).
Also, can anyone see if updating to the just released version 0.9 fixes the problem?
Albert, I tried compiling source but i am getting errors, before getting this errors solved, Is there a repo where i can find version 0.9 for debian?? Thanks
After recent update of kde-connect I can confirm everything works as expected. I think you can close this bug. Thank you for your work. It is amazing and I really appreciate it.
Albert, I haven't received yet the 0.9 update from SID debian channel, do you have any idea on when it will be available?
After every release I notify the packagers of the different distributions on a mailing list, but after that it's their choice when to release an updated package. It might help for you to ask the Debian package maintainer to release an update :)
That was my guess ;-) , I will contact them directly. Thanks