- 1 Installation
- 2 Configuration
- 3 Pairing Devices
- 4 Troubleshooting
- 5 Development
- 6 See also
KDE Connect is available for openSUSE Leap and Tumbleweed from the main repository. If you use desktop environment other than KDE's Plasma, you might also want to install indicator-kdeconnect, that provides a system tray as a GUI for other desktops.
By default, KDE Connect is installed in openSUSE Leap and Tumbleweed when installing KDE Plasma Desktop. Use the following instructions, should you need to install it.
openSUSE 1 Click Install
Instructions for copy/paste instructions into a terminal such as Konsole.
sudo zypper in kdeconnect-kde
If you are a Firefox user, this extension] might be of your interest.
In order for the secure communication to take place, ports in the firewall have to be opened up.
openSUSE Firewall Port Modifications
- Open the YaST Control Center
- Select Firewall
- Within the Firewall configuration window, select Allowed Services
- Select the Service to Allow drop-down, search for KDE Connect then Add
- On the Firewall Configuration window, select Next followed by Finish
The Firewall Service settings will save and the service will restart.
Firewalld Port Modification
The easiest way to configure firewalld is through the terminal. The other effective way is to install firewall-config and use that interface.
Note the zone your current interface. With Plasma, this is done within the Network Manager. If you do not specify the zone of the interface, it defaults to public. The example below is adjusting the default zone. For most user cases, this is an acceptable default.
sudo firewall-cmd --zone=public --permanent --add-port=1714-1764/tcp sudo firewall-cmd --zone=public --permanent --add-port=1714-1764/udp sudo systemctl restart firewalld
The packaged firewall-config must be installed to make this modification.
sudo zypper install firewall-config
- Run the application firewall-config
- Enter the root password
- The Configuration for modification defaults under Runtime. Any changes you make will only affect the current Runtime of the machine
- Note the Zone that the network is running and ensure that the current zone is selected under the Zones tab.
- In the Services tab, locate and check kdeconnect-kde in the window.
- In the Ports tab, click on Add to add the following ports
- Port/Port Range: 1714-1764, Protocol: tcp
- Port/Port Range: 1714-1764, Protocol: udp
- If you would like to make this change permanent under the selected Zone, select Options > Runtime to Permanent
- If no further changes to the firewall are required, close the Configuration window, changes are immediate.
The Firewall adjustments are complete.
Reload the Firewall by Selecting Options > Reload Firewalld
Set the device name to something that makes sense that you will recognize. This is important for the pairing process.
Most networks should allow automatic discovery of the devices running KDE Connect. Here are some things you can try if it is not automatically discovering
On the Android device select, from the menu, Add a Device by IP Should the device not show up due to services being blocked by the network you can add a device by IP
From any device, select Request Pair
Note: When pairing from Desktop to Android, be sure you are within the Android KDE Connect application
Once paired, scroll through the options to determine how much information you want communicated back and forth between devices.
Devices are running KDE Connect, but they can't see each other
- Ensure that the devices in question are on the same network
- Ensure the necessary firewall ports have been opened. If they have been opened, try restarting the firewall daemon using the YaST Firewall Tool
KDE Connect crashes or restarts when trying to pair with another device
- Some times, a corrupt config file may cause KDE Connect to crash when trying to pair with a device. In that case, deleting the config file might help.
The devices suddenly stop communicating
If both devices are on the network and the firewall is properly configured but no notifications are being displayed one or the other may device have fallen asleep. Likely the service stopped or was suspended on the mobile device.
- Open the KDE Connect settings on either device and ping the opposite or select Refresh to force connection.
You can find the sources in the following repositories: