https://bugs.kde.org/show_bug.cgi?id=358440
Nicolas Fella changed:
What|Removed |Added
CC||shanmukhat...@gmail.com
--- Comment #7 from Nic
https://bugs.kde.org/show_bug.cgi?id=358440
--- Comment #6 from Aleix Pol ---
Would it make sense to have the file installed by kde connect instead of it
being a patch by the distribution?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358440
--- Comment #5 from Rex Dieter ---
fedora's kdeconnect packaging includes a firewalld definition/profile for ports
used (per comment #2), and installs it as
/usr/lib/firewalld/services/kde-connect.xml
It's contents are:
KDE Connect
KDE Connect allow
https://bugs.kde.org/show_bug.cgi?id=358440
Aleix Pol changed:
What|Removed |Added
CC||aleix...@kde.org
--- Comment #4 from Aleix Pol ---
https://bugs.kde.org/show_bug.cgi?id=358440
Rex Dieter changed:
What|Removed |Added
Ever confirmed|0 |1
CC||
https://bugs.kde.org/show_bug.cgi?id=358440
Nick Cross changed:
What|Removed |Added
CC||k...@goots.org
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=358440
--- Comment #2 from c...@daniel.priv.no ---
The Fedora package ships with a FirewallD profile that can be turned on through
the GUI client or `firewall-cmd --add-service kde-connect`. However, it’s so
unlikely that they will enable more services by defau
https://bugs.kde.org/show_bug.cgi?id=358440
--- Comment #1 from Albert Vaca ---
In that case it would be great if you can ask the Fedora packagers to add a
script to allow kdeconnect on the firewall when it is installed. Could you
contact them?
--
You are receiving this mail because:
You are wa
