KDE Connect not connecting anymore

English Applications
#1

Hi all,
I find that KDE Connect is becoming more and more unreliable lately.
I began having problems with connecting a couple months ago, but now phone and computer don’t connect anymore.
Computer says phone is not available and the same happens the other way around.

Obviously I checked that the phone is attached to my home wifi. Both computer and phone are on the same network (phone has ip 192.168.1.181 and computer has ip 192.168.1.3).

KDEConnect on the phone is v1.6.6.
KDEConnect on the pc is v1.2.

Anybody else with this problem?
Any hints?

Thank you in advance.
Cris

#2

check the firewall maybe the firewall rules got reset by an update and the kdeconnect service is blocked
https://i.imgur.com/uhtQh8n.png
that being said if you have access to 2 smart devices you could try and pair them and see where the issue is in the android or in linux, I’ve got both my phone and tablet paired independently from my desktop as well as with my desktop and all I can say is kde-connect works flawlessly between 2 androids and between an android and linux

#3

Hi I_A!
Sorry for replying so late, somehow I did not notice your reply to my question.

Your reply prompted me to check and you were correct.
Initially I was quite doubtful because I was confusing my PC firewall rules with those of my router (I must be tired).
I don’t know why the KDE Connect rule disappeared, but now that I configured it everything is good again.

Thank you!!
Cris

#4

I do believe the firewall rules are stored in

/etc/sysconfig/SuSEfirewall2

an upgrade will overwrite that file with the default one seeing how updates are frequent on TW you should expect that that file will revert to the default sooner or latter
I’m not sure how to configure firewall rules outside that file so they persist between upgrades
https://en.opensuse.org/SuSEfirewall2
https://doc.opensuse.org/documentation/leap/security/html/book.security/cha.security.firewall.html#sec.security.firewall.SuSE

#5

That is true.

an upgrade will overwrite that file with the default one seeing how updates are frequent on TW you should expect that that file will revert to the default sooner or latter

No, an upgrade should not touch that file at all. It is a config file, and not owned by any package anyway.

#6

Hi wolfi323!

Yes, that is what I would have expected too.

However, on another PC where I have a mysql database that has to be accessible from outside, I noticed that some updates cause it to be inaccessible.
In those cases, when I open the firewall rules, the mysql rule is still there but it is not working until I reapply it.
This is probably off-topic now though.

Cris

#7

well an update did something with my /etc/sddm.conf
a bit off topic but I added

Numlock=on

to /etc/sddm.conf and after an update Numlock reverted back to off
checking my /etc dir I found 2 sddm.conf files
the old I edited sddm.conf and a new one sddm.conf.rpmnew which does not have the Numlock option
now I’m even more confused does sddm read sddm.conf.rpmnew instead of sddm.conf can sddm.conf.rpmnew be deleted
does the OP have 2 SuSEfirewall2 files as I seam to have both

/etc/sysconfig/SuSEfirewall2 and
/etc/sysconfig/SuSEfirewall2.rpmnew

where only /etc/sysconfig/SuSEfirewall2 has

FW_CONFIGURATIONS_EXT="kdeconnect-kde"

I’m guessing software upgrades install these *.rpmnew files can they be deleted is it possible they are used instead of the already present files?

#8

And what update?
I.e. what sddm version are you using?

The config handling has been drastically changed in 0.17.0 that has been released recently.

a bit off topic but I added

Numlock=on

to /etc/sddm.conf and after an update Numlock reverted back to off
checking my /etc dir I found 2 sddm.conf files
the old I edited sddm.conf and a new one sddm.conf.rpmnew which does not have the Numlock option
now I’m even more confused does sddm read sddm.conf.rpmnew instead of sddm.conf can sddm.conf.rpmnew be deleted

No, sddm only reads /etc/sddm.conf.
You can safely delete sddm.conf.rpmnew, and it shouldn’t get created anymore in the future, as we don’t ship an sddm.conf in the package anymore.
Starting with sddm 0.17.0, the default config is shipped in /usr/lib/sddm.
And you can also create a file in /etc/sddm.conf.d/ with your modifications instead of editing the main sddm.conf (which is deprecated, but should still be respected).

That’s indeed off-topic here though… :wink:

does the OP have 2 SuSEfirewall2 files as I seam to have both

I wrote in my previous reply that /etc/sysconfig/SuSEFirewall2 is not contained in any package, but it seems I was wrong:

rpm -qf /etc/sysconfig/SuSEfirewall2SuSEfirewall2-3.6.312.333-7.1.noarch

That’s an exception, normally the files in /etc/sysconfig/ are not part of any package and are only created (from templates in /var/adm/fillup-templates/) if they don’t exist yet.

I’m guessing software upgrades install these *.rpmnew files can they be deleted is it possible they are used instead of the already present files?

RPM does this automatically, if a package comes with a config file that already exists on the system (and has been modified).
It installs the config file as xxx.rpmnew then, to not overwrite the existing settings.

So the existance of a .rpmnew file does not indicate nor cause a problem.
They are not used at all.

#9

I.e. what sddm version are you using?

I’m on LEAP 42.3 running sddm 0.14

So the existance of a .rpmnew file does not indicate nor cause a problem.
They are not used at all.

OK tanks I’ll remove them
I’ll stop now as I don’t want to hijack this thread