Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43618 - [kdeconnect] Suggestion: Add post-install notice about ports used / necessary firewall rules

Attached to Project: Community Packages
Opened by Andy (andydecleyre) - Wednesday, 28 January 2015, 19:54 GMT
Last edited by Andrea Scarpino (BaSh) - Thursday, 29 January 2015, 08:33 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

For a user with a firewall enabled, it's not obvious that kdeconnect won't discover or be discovered by a kdeconnect-ready device, or why that happens when it does. It would be a kindness to inform users, post-install, that kdeconnect requires open tcp/udp ports 1714:1764.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Thursday, 29 January 2015, 08:33 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Network applications use network
Comment by Doug Newgard (Scimmia) - Thursday, 29 January 2015, 01:53 GMT
It would seem pretty obvious to me that if you're running a firewall like that, you would know that you would need to open it up for a network discovery enabled program. This seems more like Wiki information that post-install information.

Loading...