Bug 23806

Summary: KDE Connect in MCC security settings does not work
Product: Mageia Reporter: Marc Lattemann <marc.lattemann>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: mageiatools, marc.lattemann, marja11, ouaurelien, yvesbrungard
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: kdeconnect-kde-1.0.3-1.mga6 mcc CVE:
Status comment:
Bug Depends on: 21417    
Bug Blocks:    

Description Marc Lattemann 2018-11-04 22:05:49 CET
In mcc the security setting to allow KDEConnect does not not work anymore. Right now I can only access my mobile device when setting the firewall in mcc to allow everything (firewall off). Even manual adding the port ranges as described below does not work:
https://community.kde.org/KDEConnect#ufw
Marc Lattemann 2018-11-04 22:05:58 CET

CC: (none) => marc.lattemann

Comment 1 Marja Van Waes 2018-11-06 12:34:21 CET
@ KDE team

Can you look into this first, please... if anything changed on KDE side that causes this, then you'll be able to tell what that is and what needs to be changed in our tools :-)

Assignee: bugsquad => kde
CC: (none) => mageiatools, marja11

Comment 2 papoteur 2018-11-06 13:23:22 CET
Hello,
Please check first that the port 1714 is really open from a remote device.

CC: (none) => yves.brungard_mageia

Comment 3 Marc Lattemann 2018-11-06 18:52:38 CET
no seems not - from another computer:

root@Mediacenter_arch:~# nmap 192.168.1.24
Nmap scan report for Laptop (192.168.1.24)
Host is up (0.063s latency).
All 1000 scanned ports on Laptop (192.168.1.24) are filtered

Nmap done: 1 IP address (1 host up) scanned in 64.87 seconds

BTW: in former days there were notifications in the log, when shorewall rejected a connection, but journald doesn't say anything when I try to connect with my phone.
Comment 4 papoteur 2018-11-06 22:35:51 CET
Hello,
Thus the problem is the firewall which rejects all entries. Not kdeconnect.
I saw some similar report of such a behaviour.
papoteur 2018-11-06 22:40:11 CET

Depends on: (none) => 21417

Comment 5 Aurelien Oudelet 2020-08-16 21:27:23 CEST
Does this bug is still valid for Mageia 7 or Cauldron ?

CC: (none) => ouaurelien

Comment 6 Aurelien Oudelet 2020-08-26 11:15:57 CEST
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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