https://bugs.kde.org/show_bug.cgi?id=376187
Bug ID: 376187
Summary: kdeconnect.core: Error opening a port in range
1714-1764
Product: kdeconnect
Version: 1.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: bugzilla-...@ddt-consult.net
Target Milestone: ---
Since some time, my Arch Linux desktop isn't visible to my mobile devices any
more. AFAICT the culprit is kdeconnectd not being able to open network ports:
[~]$ journalctl -b _COMM=kdeconnectd
-- Logs begin at Sun 2017-01-22 20:26:10 CET, end at Wed 2017-02-08 15:43:09
CET. --
Feb 08 12:46:11 archdesktop kdeconnectd[1120]: kdeconnect.core: KdeConnect
daemon starting
Feb 08 12:46:11 archdesktop kdeconnectd[1120]: kdeconnect.core: onStart
Feb 08 12:46:11 archdesktop kdeconnectd[1120]: kdeconnect.core: Error opening a
port in range 1714-1764
Feb 08 12:46:11 archdesktop kdeconnectd[1120]: kdeconnect.core: KdeConnect
daemon started
Feb 08 12:46:36 archdesktop kdeconnectd[1120]: kdeconnect.core: Sending
onNetworkChange to 1 LinkProviders
But:
[~]$ sudo netstat -tulpn | grep :17
[~]$ sudo netstat -tupn | grep :17
[~]$ nc -l 1714
^C
[~]$ killall kdeconnectd; /usr/lib/kdeconnectd
kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: onStart
kdeconnect.core: Error opening a port in range 1714-1764
kdeconnect.core: KdeConnect daemon started
^C
[~]$
Since netstat doesn't show any port in the range 1714-1764 in use and nc can
bind to ports in this range without problems, I have no idea why kdeconnectd
fails to do so.
kdeconnect has worked well on this machine. But since I don't use kdeconnect
everyday I can't tell when exactly it has stopped working or what change on the
machine may have caused it to stop.
What can I do to find out what the problem is and (hopefully) fix it?
The machine in question is a up-to-date 64-bit Arch Linux running plasma.
--
You are receiving this mail because:
You are watching all bug changes.
