Bug 18929

Summary:	kdeconnect is not working (Process org.kde.kdeconnect received signal 6) (SIGABRT)
Product:	Mageia	Reporter:	PC LX <mageia>
Component:	RPM Packages	Assignee:	Nicolas Lécureuil <mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	geiger.david68210
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	kdeconnect-kde-0.9g-1.mga6.src.rpm	CVE:
Status comment:

Description PC LX 2016-07-12 13:44:18 CEST

Description of problem:

kdeconnect is not working. Can't connect my android devices to the system.

In a Mageia 5 system, kdeconnect is working but in the same system updated to Mageia 6 (cauldron), kdeconnect no longer works.


This is what I get in the Mageia 5 system:

$ kdeconnect-cli -l
- Pegasus: ee41913fc09ef269 
1 devices found
$ rpm -qa | grep kdeconnect | sort
kdeconnect-kde-0.8-1.mga5
lib64kdeconnectcore1-0.8-1.mga5
lib64kdeconnectinterfaces1-0.8-1.mga5


This is what I get in the Mageia 6 (cauldron) system:

$ kdeconnect-cli -l
- : Process org.kde.kdeconnect received signal 6 
1 device found
$ rpm -qa | grep kdeconnect | sort
kdeconnect-kde-0.9g-1.mga6
lib64kdeconnectcore0-0.9g-1.mga6
lib64kdeconnectinterfaces0-0.9g-1.mga6
lib64kdeconnectpluginkcm0-0.9g-1.mga6



How reproducible:

Always.



Steps to Reproduce:
1. Connect a Android device using kdeconnect to a Mageia 5 system
2. Run "kdeconnect-cli -l" to list the connected devices.
3. Update a Mageia 5 system to Mageia 6 (cauldron) and reboot.
4. Repeat steps 1 and 2 and see the differences.

Thierry Vignaud 2016-07-12 15:36:28 CEST

Assignee: bugsquad => mageia
Summary: kdeconnect is not working (Process org.kde.kdeconnect received signal 6) => kdeconnect is not working (Process org.kde.kdeconnect received signal 6) (SIGABRT)

Comment 1 David GEIGER 2016-07-25 14:36:50 CEST

I don't really know if it that or not but is kde-cli-tools installed on your system?

CC: (none) => geiger.david68210

Comment 2 Nicolas Lécureuil 2016-07-25 16:03:15 CEST

yes i think a missing deps because here i obained: 

[neoclust@localhost ~]$ kdeconnect-cli -l
- Huawei: 4d72eeec0t5ff49c (reachable)
1 device found

Comment 3 PC LX 2016-07-27 02:53:30 CEST

Yes, kde-cli-tools is installed. This bug is still present will all packages up-to-date.

$ rpm -q kde-cli-tools
kde-cli-tools-5.7.2-1.mga6

Comment 4 David GEIGER 2016-07-27 06:30:04 CEST

Ok, and is qca-qt5 installed?

Comment 5 PC LX 2016-07-27 12:40:40 CEST

That was it. The package qca-qt5 was not installed. After installing that package the issue was fixed. Thanks. Adding qca-qt5 somewhere in the dependency chain of a kdeconnect package (maybe lib64kdeconnectcore0 ?) should fix this bug.

$ rpm -q qca-qt5
package qca-qt5 is not installed
$ gurpmi qca-qt5
(...)
$ rpm -q qca-qt5
qca-qt5-2.1.1-3.mga6
$ kdeconnect-cli -l
- Pegasus: ee41913fc09ef269 (paired and reachable)
1 device found

Comment 6 Nicolas Lécureuil 2016-07-27 13:44:09 CEST

fixed in new kdeconnect-kde

Status: NEW => RESOLVED
Resolution: (none) => FIXED