Bug 1968002 - installing kde-connect should automatically create a relevant firewall allow-list for it
Summary: installing kde-connect should automatically create a relevant firewall allow-...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-connect
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Martin Bříza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-04 17:15 UTC by Nate Graham
Modified: 2023-08-16 08:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Nate Graham 2021-06-04 17:15:05 UTC
Description of problem:
KDE Connect is not allowed to communicate through the firewall, so it does not work unless the user manually disables the firewall or adds a rule allowing it. This latter option requires knowing all the technical details of which ports it communicates on, which the user is not likely to know.


Steps to Reproduce:
1. Install KDE Connect app on your Android smartphone
2. Install `kde-connect` package on your Fedora computer
3. Try to pair your phone


Actual results:
The phone can't be found from the computer, and the computer can't be found from the phone.


Expected results:
Communication between the two works with no manual firewall configuration required.


Additional info:
Disabling the firewall allows communication between the two devices, indicating that the firewall is blocking them.

I don't think there is a use case for installing KDE Connect but wanting it to be functionally broken by the firewall, so it seems like the relevant firewall port should be allowed automatically as a post-install step.

openSUSE does this, FWIW: https://bugzilla.suse.com/show_bug.cgi?id=1175627

Comment 1 Ben Cotton 2022-05-12 16:16:05 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Nate Graham 2022-05-12 17:22:04 UTC
Still an issue in 36.

Comment 3 Ben Cotton 2023-04-25 16:42:47 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Fedora Release Engineering 2023-08-16 08:08:30 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


Note You need to log in before you can comment on or make changes to this bug.