home:ecsos ! | 1.3.5 | x86_64
Pick a number (0 to quit): 1
You have selected binary package: KDE:Applications ? | 22.12.0 | x86_64
Loading repository data…
Reading installed packages…
Resolving package dependencies…
The following 2 NEW packages are going to be installed:
kdeconnect-kde kdeconnect-kde-lang
2 new packages to install.
Overall download size: 1.1 MiB. Already cached: 0 B. After the operation, additional 5.4 MiB will be
used.
Continue? [y/n/v/…? shows all options] (y):
Retrieving package kdeconnect-kde-22.12.0-lp154.43.1.x86_64 (1/2), 839.0 KiB ( 4.1 MiB unpacked)
Retrieving: kdeconnect-kde-22.12.0-lp154.43.1.x86_64.rpm …[done]
Retrieving package kdeconnect-kde-lang-22.12.0-lp154.43.1.noarch
(2/2), 325.5 KiB ( 1.4 MiB unpacked)
Retrieving: kdeconnect-kde-lang-22.12.0-lp154.43.1.noarch.rpm …[done]
Checking for file conflicts: …[done]
(1/2) Installing: kdeconnect-kde-22.12.0-lp154.43.1.x86_64 …[done]
(2/2) Installing: kdeconnect-kde-lang-22.12.0-lp154.43.1.noarch …[done]
linux:~ #
(By the way -haven’t you the code tags any more?)
Now when I try to transfer files and open KDEconnect on this computer I get the following
As you can see when I open KDEconnect all it does is it asks whether I want to install it from GooglePlay or Fdroid. The button 'pair a device" and the settings button don’t work. Why does LEAP15.4 want to install android versions after installing a KDE Application?
The two lower buttons are only hints that you need to install KDEConnect also to your mobile device.
To be able to pair two devices, on both devices KDEConnect needs to be opened and they need to be in the same network. Also make sure that the firewall isn’t interfering.
Yes, they’re here – the “</>” «Preformatted text (Ctrl+E)» button – above the text box where one types replies – 6th from left –
> timedatectl
Local time: Mo 2022-12-19 12:06:30 CET
Universal time: Mo 2022-12-19 11:06:30 UTC
RTC time: Mo 2022-12-19 11:06:31
Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
>
Thank you, hui, but the computer does not see the mobile with KDEconnect on anc vice versa. I cannot go to the settings because that button does not work either. And of course I cannot pair a device since it does not see one. It works OK on another Leap15.4 computer with any of our phones. So it has to be something with the kdeconnect on that computer. I will try with the firewall next.
There has to be something wrong. I added kdeconnect at the firewall and restarted firewalld.service and it makes no difference. The only buttons working are to install from google play or Fdroid. When I click them the Browser opens up with e.g. Googleplay… All other buttons are not working and I am not seeing any other device with kdeconnect on.
Try in firewall zone click public and add kdeconnect.
Then if it is connected maybe someone can advice you better where kdeconnect has to be in the firewall zone.
What are you using kdeconnect for. Is it for a cellphone or another device. You haven’t mentioned it.
Please tell what do you want to use for kdeconnect. I was able to use it on iphone sometime ago, haven’t use it for a while. As hui mentioned both sides should be in the same network and both your machine and the device you are intending to use should be on and kdeconnect application on both sides are open.
We use it mainly to transfer photos from the phone to the computer. We have used KDEconnect with this for many years. Of course they have to be on the same network. The phones are on Wifi and the computer either on ethernet or Wifi or both. We have 4 computers running Leap15.4 on the network but this new installed one (and most modern one) causes problems.
I prefer to let the Pocket Telephone perform the Connect Request – on your KDE Plasma Desktop you’ll see a request like this:
Accept the request and then on the KDE Plasma Desktop you’ll see something like this:
Set it up – decide where files sent from the Pocket Telephone should land in your Linux environment.
Be aware that, for the case of files sent from KDE Plasma to the Pocket Telephone you’ll have to search with Android “Files” or whatever, to find out where the uploaded files have been dropped …
What happens if you turn off the firewall? Can you pair the phone?
Do you also allow kdeconnect-kde or only kdeconnect?
I have kdeconnect and kdeconnect-kde in the public zone
So the following has changed. When I open KDEconnect from the computer it looks like this:
No longer the install from GooglePlay etc. buttons. However when I click Settins nothing happens. When I go to systemsettings5 and open the KDEconnect settings it looks like that:
That’s whot I would expect when clicking the settings button. (I don’t know why the router always insists to put fritz.box in the computer name. Did it with another computer as well. But the file /etc/hostname is empty and the hostname command only shows the same name.)
Now I can see the computer from KDEconnect on the phone and send a pair request. The phone says request timed out but the computer shows the devices as paired:
However when I open dolphin and select SM-A022F to check if the devices are really paired I don’t see anything and the phone insists that the devices are not paired. Clicking “Send Ping” does not do anything.
So I would say it is not the firewall but something in the KDEconnect settings.
Difficult to tackle. I see you have two phones. Do they see each other when kdeconnect is active on both? They should.
Is the kdeconnectd service active?
This happens because, an AVM FRITZ!Box uses the Domain “fritz.box” for the private LAN and private WLAN managed by the Router.
Yes, the TLD “.box” is a problem but, AFAIK, the company in Berlin with the name “AVM” have managed to resolve the issues around using this TLD for private networks …
If you had clicked “Pair a Device…” you would have seen something like this for every Android Pocket Telephone on your WLAN which has the KDE Connect app installed:
After the Pocket Telephone has been “paired” (the security keys have to be setup), it has to be “connected” – by sending a Connect Request, which has to be confirmed …
I allowed kdeconnect
