| Summary: | kdeconnect.interfaces: dbus interface not valid | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Knut Hildebrandt <post> |
| Component: | desktop-application | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Chakra | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Knut Hildebrandt
2019-06-15 07:15:59 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. 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? |