Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux.mint > #47501 > unrolled thread

KDE connect

Back to article view | Back to alt.os.linux.mint

Contents

  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

Page 1 of 2  [1] 2  Next page →

#47501 — KDE connect

  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!

-- 
Linux Mint 22.3

[toc] | [next] | [standalone]

#47502

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!
>

p.s I just found https://userbase.kde.org/KDEConnect maybe something 
there will help

-- 
Linux Mint 22.3

[toc] | [prev] | [next] | [standalone]

#47503

Le 16/05/2026 à 05:25, Axel a écrit :
>   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!
> 

just i question :

do you have wifi on your machine ?
you can to surf with a wifi partage ?

-- 
Amicalement,

Frenchy Friendly, & French touch !

german

[toc] | [prev] | [next] | [standalone]

#47504

Le 16/05/2026 à 05:25, Axel a écrit :
>   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!
> 

what you can to do with Applet NetworkManager ?

you see it on task barre ?


-- 
Amicalement,

Frenchy Friendly, & French touch !

german

[toc] | [prev] | [next] | [standalone]

#47506

On 5/16/26 5:25 AM, 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.

No you did not :-)

  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!

Never heard of KDEconnect but I once tried a KDE application on a MATE 
system and it broke my computer.
If there is anything else then KDE I would quickly switch to that.

Not much help but a good advice



-- 
Once an organization gains any influence, it will be corrupted from both 
within and without.

Edmund

[toc] | [prev] | [next] | [standalone]

#47507

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.

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

Is the daemon running ? 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.

Do both Device1 and Device2, see Device3, and yet do not see each other
(as evidence of a "network partition") ?

You've probably done some of this already.

    https://discuss.kde.org/t/troubleshooting-kdeconnectd-on-linux/27743

I would say "use Wireshark", but the modality might not have a promiscuous
receiver to use.

Some protocols have had good penetrating power. The original Skype
was pretty good at going places you would not expect. Commercial
companies (at first), could not stop it :-) The few details I've
collected so far, do not suggest this uses the same "design style".
It's going to need help, in some cases.

    Paul

[toc] | [prev] | [next] | [standalone]

#47512

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? :)

>
> Some protocols have had good penetrating power. The original Skype
> was pretty good at going places you would not expect. Commercial
> companies (at first), could not stop it :-) The few details I've
> collected so far, do not suggest this uses the same "design style".
> It's going to need help, in some cases.
>
>      Paul


-- 
Linux Mint 22.3

[toc] | [prev] | [next] | [standalone]

#47518

Axel wrote:
> Motorola G84 5g phone model

Android 13; go to Google Play store for a KDE connect for it.

https://play.google.com/store/search?q=kde%20connect&c=apps&hl=en_US

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]

#47524

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
whining...

     Paul

[toc] | [prev] | [next] | [standalone]

#47529

On Sat, 16 May 2026 13:14:45 -0400, Paul wrote:

> 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.

Of course systemd rules will help. This is a per-user service, not a
systemwide service. systemd knows how to handle those too, you know.

    systemctl status --user '*kde*'

[toc] | [prev] | [next] | [standalone]

#47538

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

[toc] | [prev] | [next] | [standalone]

#47543

On 5/17/26 4:48 AM, Axel wrote:
> 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
> 
> 
You know, all browsers and android can be loaded with Pushbullet.   You do a bit of setup 
on both ends, the browser and the android app.   You need to make a login.   Once 
connected you can send/receive text messages and see any notifications.
As for file transfer, I use a 'file manager+' in productivity.
https://play.google.com/store/apps/details?id=com.alphainventor.filemanager&hl=en-US&pli=1

One of it's options is 'access to network'.  When started, it becomes an FTP file server. 
Load a client like filezilla and put in the appropriate host name etc that the app gives 
you when started and you can upload and download via your PC.  Whole directories, or files.

I find it quite simple.


-- 
Mint 22.3,  Thunderbird 140.10.2esr,  Firefox 150.0.3
     Alan K.

[toc] | [prev] | [next] | [standalone]

#47545

On Sun, 17 May 2026 18:48:11 +1000, Axel wrote:

> 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.

Fwiw I set up KDE Connect on the Fedora box and got the app for the 
Samsung A16. Other than having to turn on wifi for the phone it seems to 
work. I'd rather it use Bluetooth but I'm not sure that's an option. 
Connect crashes when I try.

[toc] | [prev] | [next] | [standalone]

#47516

Axel wrote:
>   I cannot get it to see the LM PC !

If I were wanting a KDE Connect on a LM 22.3 such as Cinnamon, I would 
choose a similar function based on my DE's toolkit GTK, such as GS 
Connect.  That way I don't have to drag in all of that Qt stuff.

https://extensions.gnome.org/extension/1319/gsconnect/

There is a lot of clutter and 'confusion' created by throwing in a 
different system like KDE apps based on Qt when LM isn't.

And, if I were 'curious' about KDE Connect, I would boot a live KDE 
distro (not LM) to see how it works.



-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]

#47517

Mike Easter wrote:
> If I were wanting a KDE Connect on a LM 22.3 such as Cinnamon, I would 
> choose a similar function based on my DE's toolkit GTK, such as GS 
> Connect.  That way I don't have to drag in all of that Qt stuff.

Oops. I posted that before reading about the idea.

Advisors say that Gnome-based GS Connect is *WORSE* than KDE Connect on 
a LM such as Cinnamon because GS is TOO Gnome-specific, whereas KDE 
Connect is supposed to be more independent of DE.

So, I 'take all that I said' back.

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]

#47520

Mike Easter wrote:
> Advisors say that Gnome-based GS Connect is *WORSE* than KDE Connect on 
> a LM such as Cinnamon because GS is TOO Gnome-specific, whereas KDE 
> Connect is supposed to be more independent of DE.

Cinnamon and the other LM DEs have departed SO FAR from Gnome, that such 
as the Gnome Extensions, including GS Connect, aren't compatible, 
regardless of having similar toolkit base in GTK.

-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]

#47522

On Sat, 5/16/2026 11:47 AM, Mike Easter wrote:
> Mike Easter wrote:
>> If I were wanting a KDE Connect on a LM 22.3 such as Cinnamon, I would choose a similar function based on my DE's toolkit GTK, such as GS Connect.  That way I don't have to drag in all of that Qt stuff.
> 
> Oops. I posted that before reading about the idea.
> 
> Advisors say that Gnome-based GS Connect is *WORSE* than KDE Connect on a LM such as Cinnamon because GS is TOO Gnome-specific, whereas KDE Connect is supposed to be more independent of DE.
> 
> So, I 'take all that I said' back.
> 

When you install packages, you're supposed to note what the interface
says about quantity-o-bytes and "list of packages to install". If the
list is ridiculously long, that's your first hint you've invited
Martian Invaders into the house. I've NACKed out of a package
install many times, on seeing just how large the package set
that I'm about to install is going to be.

The thing is, Axel is trying to get everything running on a
single unified solution.

   Paul

[toc] | [prev] | [next] | [standalone]

#47523

Paul wrote:
> When you install packages, you're supposed to note what the interface
> says about quantity-o-bytes and "list of packages to install". If the
> list is ridiculously long, that's your first hint you've invited
> Martian Invaders into the house. I've NACKed out of a package
> install many times, on seeing just how large the package set
> that I'm about to install is going to be.
> 
Well, on the one hand, I was right about KDE Connect requiring a LOT of 
stuff related to KDE that is NOT on a default LM.

But, OTOH, installing KDE Connect on LM 22.3 Cinnamon does result in a 
'family' of KDE Connect apps in its menu which seem worthwhile, KDE 
Connect (make all your devices one), KDE Connect indicator (display info 
about your devices), KDE Connect settings (which window says, 'If you 
own an Android device, make sure to install the KDE Connect Android app 
(also available from F-Droid) and it should appear in the list (also 
directions to help from kdec wiki) and KDE Connect SMS texting.

> The thing is, Axel is trying to get everything running on a
> single unified solution.

So far, I'm now advising KDE Connect on LM 22.3 such as Cinn AND KDE 
Connect from Google Play on his Android Moto device.


-- 
Mike Easter

[toc] | [prev] | [next] | [standalone]

#47537

Mike Easter wrote:
> Paul wrote:
>> When you install packages, you're supposed to note what the interface
>> says about quantity-o-bytes and "list of packages to install". If the
>> list is ridiculously long, that's your first hint you've invited
>> Martian Invaders into the house. I've NACKed out of a package
>> install many times, on seeing just how large the package set
>> that I'm about to install is going to be.
>>
> Well, on the one hand, I was right about KDE Connect requiring a LOT 
> of stuff related to KDE that is NOT on a default LM.
>
> But, OTOH, installing KDE Connect on LM 22.3 Cinnamon does result in a 
> 'family' of KDE Connect apps in its menu which seem worthwhile, KDE 
> Connect (make all your devices one), KDE Connect indicator (display 
> info about your devices), KDE Connect settings (which window says, 'If 
> you own an Android device, make sure to install the KDE Connect 
> Android app (also available from F-Droid) and it should appear in the 
> list (also directions to help from kdec wiki) and KDE Connect SMS 
> texting.
>
>> The thing is, Axel is trying to get everything running on a
>> single unified solution.
>
> So far, I'm now advising KDE Connect on LM 22.3 such as Cinn AND KDE 
> Connect from Google Play on his Android Moto device.
>
>

I have installed it on another LM machine, and it's great

-- 
Linux Mint 22.3

[toc] | [prev] | [next] | [standalone]

#47539

On Sun, 5/17/2026 4:31 AM, Axel wrote:
> Mike Easter wrote:
>> Paul wrote:
>>> When you install packages, you're supposed to note what the interface
>>> says about quantity-o-bytes and "list of packages to install". If the
>>> list is ridiculously long, that's your first hint you've invited
>>> Martian Invaders into the house. I've NACKed out of a package
>>> install many times, on seeing just how large the package set
>>> that I'm about to install is going to be.
>>>
>> Well, on the one hand, I was right about KDE Connect requiring a LOT of stuff related to KDE that is NOT on a default LM.
>>
>> But, OTOH, installing KDE Connect on LM 22.3 Cinnamon does result in a 'family' of KDE Connect apps in its menu which seem worthwhile, KDE Connect (make all your devices one), KDE Connect indicator (display info about your devices), KDE Connect settings (which window says, 'If you own an Android device, make sure to install the KDE Connect Android app (also available from F-Droid) and it should appear in the list (also directions to help from kdec wiki) and KDE Connect SMS texting.
>>
>>> The thing is, Axel is trying to get everything running on a
>>> single unified solution.
>>
>> So far, I'm now advising KDE Connect on LM 22.3 such as Cinn AND KDE Connect from Google Play on his Android Moto device.
>>
>>
> 
> I have installed it on another LM machine, and it's great
> 

https://unix.stackexchange.com/questions/524502/kde-connect-not-working-ubuntu-16-04-kde-connect-is-not-discovering-phone-an

    ~/.config/kdeconnect    <=== configuration file

The article there is old, but it is claiming the software may have
an attachment to the use of IPV6. Yet, your other stuff works, so if there
was an issue, all should have been affected the same. On purpose, my
router uses IPV4 only :-)

The commands and approach in the article are also old, like smacking
stuff around with killall and such :-)

Since some of your stuff works and only a few things don't, that
makes it more likely some difference in firewall might be the problem.

You can see the person there, using ps with some options, then grepping
on kdeconnectd. And finding the daemon running from the expected place.

   $ ps -eat | grep kdeconnectd

   00:00:00 /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd

*******

Some network functions are similar to the following , in that they attach some
significance to a program or function, rather than insisting
the user type these rules in manually. At one time, we might name
eight different ports, and expect the user to program things
like a firewall by hand. But now, just like a .desktop file for
program launch, the firewall can be configured as programs need
port ranges.

[kdeconnect]

title=KDE Connect
description=Device Synchronization
ports=1714:1764/udp|1714:1764/tcp

TCP is a reliable three packet kind of protocol, whereas
UDP is a single packet/roll-your-own-reliability kind of
choice. UDP might work on a home wired LAN, where the odds of
a packet getting lost are minimal. Whereas a packet going from
my house to Finland, needs reliable transport and there
are some odds the packet might not arrive at the destination.
KDEConnect is really intended for local use, but transport
over Wifi might not be perfectly reliable, so I could see
TCP being used for that case. It would retry, if the ACK did not
come back.

One of the reasons we try to solve problems, is to become
more familiar with the subsystems in the computer. It's supposed
to make solving the next problem, easier :-) An investment
in the future.

   Paul

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | alt.os.linux.mint

csiph-web