Bug 408723 - kdeconnect.interfaces: dbus interface not valid
Summary: kdeconnect.interfaces: dbus interface not valid
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeconnect
Classification: Applications
Component: kcm (show other bugs)
Version: unspecified
Platform: Chakra Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-15 07:15 UTC by Knut Hildebrandt
Modified: 2019-11-05 11:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Hildebrandt 2019-06-15 07:15:59 UTC
SUMMARY
Since the update of kdeconnect to 1.3.x - I mean all versions - kdeconnect always crashes when connecting to the android phone (1.12.7).



STEPS TO REPRODUCE
1. start kdeconnect in systemsettings
2. search for other devices
3. connect to android phone

OBSERVED RESULT
notification tells me that kdeconnect crashed

EXPECTED RESULT
devices connect


This is a long lasting problem that does not occur when I go back to kdeconnet 1.2.1. Thus I suppose Plasma and Framworks version don't play a role. Here they are anyway.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58
Qt Version: 5.12.3

ADDITIONAL INFORMATION

I started systemsettings from command line and got this message when kdeconnect crashed while connecting

kdeconnect.interfaces: dbus interface not valid
Comment 1 Knut Hildebrandt 2019-07-31 07:09:07 UTC
Just upgraded to 3.5 hoping the crashes got fixed, but they did not. I'm not sure if it is the same issue but here what I did to reproduce it.

1. kdeconnect stopped on both devices

2. start kdeconnect on the laptop

$ LC_ALL=C /usr/lib/kdeconnectd
kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: onStart
kdeconnect.core: KdeConnect daemon started
kdeconnect.core: Broadcasting identity packet

3. start kdeconnect (1.12.93) on smart phone

QObject::connect: No such slot LanLinkProvider::connectError()
QObject::disconnect: No such slot LanLinkProvider::connectError()
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
QObject::connect: No such slot LanLinkProvider::connectError()
QObject::disconnect: No such slot LanLinkProvider::connectError()
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a new device "motorola"
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a known device "motorola"

4a. laptop is found on smartphone thus I tried connecting from smart phone

kdeconnect.core: creating pairing handler for "906f7fd28384c43b"
kdeconnect.core: Pair request

5a. accepting pairing request on laptop

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeconnect.plugin.mpris: MPRIS service "org.mpris.MediaPlayer2.clementine" just came online
kdeconnect.plugin.mpris: Mpris addPlayer "org.mpris.MediaPlayer2.clementine" -> "Clementine"
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "motorola"
KCrash: Application 'kdeconnectd' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...

[1]+  Stopped              LC_ALL=C /usr/lib/kdeconnectd

$ Unable to start Dr. Konqi
Re-raising signal for core dump handling.

[1]+  Speicherzugriffsfehler  (Speicherabzug geschrieben) LC_ALL=C /usr/lib/kdeconnectd

4b. smartphone on laptop found thus I tried connection from laptop

kdeconnect.core: Sending onNetworkChange to  1  LinkProviders
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: Unserialization error: "unterminated string"
kdeconnect.core: Starting client ssl (but I'm the server TCP socket)
kdeconnect.core: Socket succesfully stablished an SSL connection
kdeconnect.core: It is a known device "motorola"
kdeconnect.core: creating pairing handler for "906f7fd28384c43b"
Device pairing error "Timed out"


I could not establish a connection neither way and went back to 1.2.1 that works flawless.
Comment 2 Knut Hildebrandt 2019-11-05 11:21:35 UTC
Same problem with 1.3.5-1 but I got it eventually working.

Deactivated all modules and re-acitvated them one by one. Kdeconnect crashed immediately after activating "Host remote commands" which is installed with version 0.1. There is another module called "Befehle ausführen" which means "Execute commands" - don't now the exact name - and has version 0.1 too. Big difference, in the latter module I can configure the command I want to execute on my computer. And this works perfectly. Thus I keep this one activated and the other one deactivated. Only question I have, how can I get rid of the not working module?