https://bugs.kde.org/show_bug.cgi?id=383004
--- Comment #3 from Fabian Vogt <fab...@ritter-vogt.de> --- (In reply to Albert Vaca from comment #2) > If kdeconnect is already running, launching kdeconnectd again should just > exit immediately. I'm not sure why this is not happening. Can you check if, > while your desktop is already up, running kdeconnectd by hand also hangs? Or > it does just exit as intended? I'm trying to understand if this happens > always under your setup or just while the desktop is starting. It hangs as well, as expected. I rechecked, it's actually solely the bluetooth support's fault. Due to the blocking wait in BluetoothLinkProvider::BluetoothLinkProvider() the first instance does not answer to the pings sent by the second instance in time. -- You are receiving this mail because: You are watching all bug changes.
