Re: KDE connect

From	Axel <none@not.here>
Newsgroups	alt.os.linux.mint
Subject	Re: KDE connect
Date	2026-05-17 18:48 +1000
Message-ID	<n6tdmbFht8dU2@mid.individual.net> (permalink)
References	<n6q6diF2h1oU1@mid.individual.net> <10u97t7$ql4g$1@dont-email.me> <n6r5d4F72q3U1@mid.individual.net> <10ua8m4$146mi$1@dont-email.me>

Show all headers | View raw

Paul wrote:
> On Sat, 5/16/2026 8:14 AM, Axel wrote:
>> Paul wrote:
>>> On Fri, 5/15/2026 11:25 PM, Axel wrote:
>>>> I cannot get it to see the LM PC !
>>>> at this point I am tearing my hair out, except I don't have any!
>>>>
>>>> I have tried everything. I put in the firewall rules, it's connected
>>>> to same network, tried the manual connect with IP address (phone pings
>>>> LM in 12 ms), uninstalled KDEconnect (with purge), reinstalled it after reboot,
>>>> and whatever else i can't remember.
>>>>
>>>> My phones connect to each other and a windows PC just fine.
>>>>
>>>> What else can I do other than tearing hair out I don't have!
>>> Indicate the DE as well.
>> sorry, as per my sig LM22.3 (cinnamon)
>>
>>> linuxmint-22.3-cinnamon-64bit.iso                  08-Jan-2026 18:32      3G
>>> linuxmint-22.3-mate-64bit.iso                      08-Jan-2026 20:53      3G
>>> linuxmint-22.3-xfce-64bit.iso                      08-Jan-2026 21:09      3G
>>> lmde-7-cinnamon-64bit.iso                          07-Oct-2025 16:21      3G
>>>
>>> What is your presumed comms channel, and the device at each end ?
>>>
>>>              details-of-network
>>>           +-----------------------+
>>>           |                       |
>>>        Device1                 Device2
>> Asus PC running LM 22.3.   Motorola G84 5g phone model
>>
>>> Is the daemon running ?
>> I don't know what you're asking
>>
>>>    The state of the application on each
>>> end, hints at how much of each ecosystem is populated and running.
>>> Also, when you hint that the Application is running and can see
>>> other devices, that knocks out a number of possibilities on
>>> at least one end.
>> yes, the problem is with the LM PC I believe. the phone running KDEc sees other phones and the w11 PC running the app.
>>
>>> Do both Device1
>> device 1 sees nothing. device 2 sees other devices, as above
>>
>>> and Device2, see Device3, and yet do not see each other
>> phones see each other and the w11 PC
>>
>>> (as evidence of a "network partition") ?
>>>
>>> You've probably done some of this already.
>>>
>>>       https://discuss.kde.org/t/troubleshooting-kdeconnectd-on-linux/27743
>> no, I hadn't seen that, thanks. I will check it out
>>
>>> I would say "use Wireshark",
>> I will look into that
>>
>>>    but the modality might not have a promiscuous
>>> receiver to use.
>> ??? is that something to do with hookers? :)
> Wireshark has Ethernet-Capture and USB-Capture, it may have Wifi-Capture
> or that could be an add-on, but it may lack a way of working with
> Bluetooth to Bluetooth connections. While your phone could be tethered
> with a cable and using rndis or something, it's more likely you are
> using the Wifi on your phone.
>
> Promiscuous receiver, means the driver (on a shared media) can
> "listen" to all conversations, instead of a restricted set of conversations
> when debugging.
>
> So we have your picture now. Something like this.
>
>                      Wifi-Router  (Does Wireshark handle Wifi ?)
>                     /           \
>            +--------             -------+
>            |                            |
>         LM223 Cinn                    Motorola G84 5g
>         DesktopPC
>
> The daemon mentioned is in the URL-text.
>
>      troubleshooting - kdeconnectd     # A daemon is name-of-software with a "d" on the end :-)
>
> and is kdeconnectd. That is a process with some degree of elevation,
> that runs as a service all the time, and it is going to route something
> from one machine to another machine. Since a series of ports were set
> aside, it likely keeps track of port usage and the "sessions"
> associated with that. For example, your LM223 Cinnamon could have two
> phones KDEConnected at the same time, and then a different port
> would be used for each one. A similar kind of thing happens
> when you have two X11 sessions, one might be on port 6000, the other
> on port 6001 and up to 64 ports are set aside for that usage.
>
> The systemd has status checks for daemons. But while we have some
> explanations of bits and pieces of the setup here...
>
>     https://discuss.kde.org/t/troubleshooting-kdeconnectd-on-linux/27743
>
> there is some more indication of the foreign-ness of it here.
>
>     https://askubuntu.com/questions/829628/how-to-disable-kdeconnectd-autostart
>
>         Any systemd rules won't help, as this daemon starts via dbus.
>
> A process status command, should show this running as the kdeconnectd daemon.
>
>     /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
>
> and it will have a PID (process ID) or whatever. I'm sure someone
> can craft something better than this. This is just muscle-memory for
> me from Unix days.
>
>     ps aguwwwx | grep -i kdeconnect    # sweep for app and daemon
>
> I don't know the answer to your problem -- firewall sounds logical.
> with Wireshark running, you could reverse the situation, and
> see if the phone "trying to connect the PC" works. Then look at
> the Wireshark trace on the LM223 Cinn PC and see if the packets
> are arriving or not.
>
> If kdeconnectd was not running, the application portion should
> whine that it cannot connect to the daemon. I expect, since you
> did not note anything like that, that indeed kdeconnectd is
> running. It's still possible for it to be "struck dumb", if it
> cannot get the resources it needs. Then you'd have to track
> down the log that kdeconnectd dumps, and see if *it* is

I've given up on this. it's all too complicated for me to bother with. 
I'm just not that interested in learning new stuff, and troubleshooting 
and diagnosing faults (too old), I just want a computer that works. so I 
will revert to plugging in a cable to transfer files. (sigh) pity, 
because KDEc works great on other LM and windoze PC's. there's obviously 
just some weird fault with this one.

> whining...
>
>       Paul


-- 
Linux Mint 22.3

Back to alt.os.linux.mint | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

KDE connect Axel <none@not.here> - 2026-05-16 13:25 +1000
  Re: KDE connect Axel <none@not.here> - 2026-05-16 13:31 +1000
  Re: KDE connect german newsgroups <usualsuspectrider@gmail.com> - 2026-05-16 06:32 +0200
  Re: KDE connect german newsgroups <usualsuspectrider@gmail.com> - 2026-05-16 06:33 +0200
  Re: KDE connect Edmund <nomail@hotmail.com> - 2026-05-16 09:50 +0200
  Re: KDE connect Paul <nospam@needed.invalid> - 2026-05-16 03:55 -0400
    Re: KDE connect Axel <none@not.here> - 2026-05-16 22:14 +1000
      Re: KDE connect Mike Easter <MikeE@ster.invalid> - 2026-05-16 08:58 -0700
      Re: KDE connect Paul <nospam@needed.invalid> - 2026-05-16 13:14 -0400
        Re: KDE connect Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-17 05:22 +0000
        Re: KDE connect Axel <none@not.here> - 2026-05-17 18:48 +1000
          Re: KDE connect "Alan K." <alan@invalid.com> - 2026-05-17 11:52 -0400
          Re: KDE connect rbowman <bowman@montana.com> - 2026-05-17 17:39 +0000
  Re: KDE connect Mike Easter <MikeE@ster.invalid> - 2026-05-16 08:43 -0700
    Re: KDE connect Mike Easter <MikeE@ster.invalid> - 2026-05-16 08:47 -0700
      Re: KDE connect Mike Easter <MikeE@ster.invalid> - 2026-05-16 09:13 -0700
      Re: KDE connect Paul <nospam@needed.invalid> - 2026-05-16 12:43 -0400
        Re: KDE connect Mike Easter <MikeE@ster.invalid> - 2026-05-16 09:57 -0700
          Re: KDE connect Axel <none@not.here> - 2026-05-17 18:31 +1000
            Re: KDE connect Paul <nospam@needed.invalid> - 2026-05-17 07:54 -0400
        Re: KDE connect Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-16 23:41 +0000
          Re: KDE connect Monsieur <Monsieur@notreal.invalid> - 2026-05-17 08:00 +0200

csiph-web