https://bugs.kde.org/show_bug.cgi?id=383004
--- Comment #1 from Fabian Vogt <[email protected]> --- I debugged a bit further and found the issue. Both /etc/xdg/autostart/kdeconnect.desktop org.kde.plasmashell.desktop are autostart phase 0, so they might be started in either order. If plasmashell is started first, it triggers the dbus-activation and kdeconnect is started by the session dbus-daemon. Then ksmserver starts /etc/xdg/autostart/kdeconnect.desktop, which locks up as it found that org.kde.kdeconnectd is already registered. Deleting /etc/xdg/autostart/kdeconnect.desktop helps and is likely the right solution here. However, this doesn't solve the problem entirely, as now kdeconnectd hangs inside the experimental bluetooth code: #0 0x00007f1ca5a1d5dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1ca9c0504b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x00007f1ca88dc83b in QDBusPendingCallPrivate::waitForFinished() () from /usr/lib64/libQt5DBus.so.5 #3 0x00007f1ca837aab4 in isBluez5 () at bluez/bluez5_helper.cpp:74 #4 0x00007f1ca838d5d8 in QBluetoothServiceInfoPrivate::QBluetoothServiceInfoPrivate (this=0x560b034100a0) at qbluetoothserviceinfo_bluez.cpp:180 #5 0x00007f1ca835894e in QBluetoothServiceInfo::QBluetoothServiceInfo (this=0x560b03411b50) at qbluetoothserviceinfo.cpp:345 #6 0x00007f1cabc5411f in BluetoothLinkProvider::BluetoothLinkProvider() () from /usr/lib64/libkdeconnectcore.so.1 #7 0x00007f1cabc73042 in Daemon::Daemon(QObject*, bool) () from /usr/lib64/libkdeconnectcore.so.1 #8 0x0000560b01aff1a5 in ?? () #9 0x00007f1ca944446a in __libc_start_main () from /lib64/libc.so.6 #10 0x0000560b01aff24a in _start () -- You are receiving this mail because: You are watching all bug changes.
