LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   how to disable kdeconnectd (https://www.linuxquestions.org/questions/slackware-14/how-to-disable-kdeconnectd-4175618933/)

Aeterna 12-04-2017 08:01 AM

how to disable kdeconnectd
 
Hello,
Is there any way to disable kdeconnectd?
In plasma settings I see only option to connect to Android. But I don't see a way to stop it listening on tcp/udp 1716

thank you

Alien Bob 12-04-2017 12:37 PM

System Settings > Startup and Shutdown > Service Manager > Startup Services.
There you un-check the "KDE Connect" service so that it no longer starts automatically when you login.

Aeterna 12-04-2017 04:24 PM

Quote:

Originally Posted by Alien Bob (Post 5788728)
System Settings > Startup and Shutdown > Service Manager > Startup Services.
There you un-check the "KDE Connect" service so that it no longer starts automatically when you login.


Thank you very much,

Unfortunately this option is not available anymore although I was using this setting before
System Settings > Startup and Shutdown >
Service Manager -> not present/not available

https://ibb.co/hMz7cw

Alien Bob 12-04-2017 04:47 PM

So you are not using the KDE4 of Slackware then. Plasma5 instead? You should mention that you run a customized setup if you post in this forum.

Aeterna 12-04-2017 05:03 PM

Quote:

Originally Posted by Alien Bob (Post 5788858)
So you are not using the KDE4 of Slackware then. Plasma5 instead? You should mention that you run a customized setup if you post in this forum.

this is exactly what my first post says

Quote:

Originally Posted by Aeterna (Post 5788583)
Hello,
Is there any way to disable kdeconnectd?
In plasma settings I see only option to connect to Android. But I don't see a way to stop it listening on tcp/udp 1716

thank you


Alien Bob 12-04-2017 05:25 PM

Quote:

Originally Posted by Aeterna (Post 5788868)
this is exactly what my first post says

Nope, at a minimum it was ambiguous. The desktop environment in KDE4 was already called Plasma, and it was developed further into Plasma 5 (at which time the acronym KDE5 was dropped and Plasma5 became the norm).
If you use a non-standard installation please always mention in what ways you are deviating from a regular Slackware installation (I installed product X from location Y).

Aeterna 12-04-2017 05:37 PM

Quote:

Originally Posted by Alien Bob (Post 5788881)
Nope, at a minimum it was ambiguous. The desktop environment in KDE4 was already called Plasma, and it was developed further into Plasma 5 (at which time the acronym KDE5 was dropped and Plasma5 became the norm).
If you use a non-standard installation please always mention in what ways you are deviating from a regular Slackware installation (I installed product X from location Y).

I like your Plasma but, this tread is just becoming useless bickering going nowhere.
This is some sort of annoying fashion at LQ?


I noticed though that Funtoo latest KDE does not have Service Manager either.

Problem "solved"

heyjann 12-04-2017 05:39 PM

If you are using any custom packages that replace regular Slackware packages with the same name, the number of people who might know the answer will be much lower. Best hinted at in post title itself.

Anyway...

Does the file /etc/kde/xdg/autostart/kdeconnectd.desktop exist on your system? If so, it'd be the first file I'd try modifying (/sabotaging).

According to this page, a Hidden = true setting disables autostarting:
https://github.com/vasi/kdelibs/blob...ADME.autostart

Aeterna 12-04-2017 06:46 PM

Quote:

Originally Posted by heyjann (Post 5788886)
If you are using any custom packages that replace regular Slackware packages with the same name, the number of people who might know the answer will be much lower. Best hinted at in post title itself.

Anyway...

Does the file /etc/kde/xdg/autostart/kdeconnectd.desktop exist on your system? If so, it'd be the first file I'd try modifying (/sabotaging).

According to this page, a Hidden = true setting disables autostarting:
https://github.com/vasi/kdelibs/blob...ADME.autostart

Thank you.

None of the options listed in the link you provided solves the issue. Probably the reason why funtoo has kdeconnectd as a separate module tha user can install if needed or not.

heyjann 12-04-2017 07:31 PM

Then the plasma5 desktop might not have much of a dependency on it at all, maybe try a hammer and see if slackpkg remove kdeconnect breaks anything?

Alternatively, you might investigate if some config file somewhere in your /home dir might also be autostarting it. And/or really sabotage /etc/kde/xdg/autostart/kdeconnectd.desktop (it did exist, right? I'd expect that that is the file that makes it autostart), have it try to autostart "Exec=kde_not_connectd" so it'll fail.

I might do some testing myself later.

Gordie 12-04-2017 09:00 PM

That little arrow next to the clock in the tray. Right button click and choose System Tray Settings. Look at Extra Items for KDE Connect

Aeterna 12-05-2017 07:50 AM

thank you both for suggestions:

so editing /etc/kde/xdg/autostart/kdeconnectd.desktop did nothing

Quote:

That little arrow next to the clock in the tray. Right button click and choose System Tray Settings. Look at Extra Items for KDE Connect
No, unfortunately KDE Connect was unchecked.
Which makes sense because I believe that kdeconnectd.desktop file just refers to the KDE Connect applet that was inactivated anyway (I never used it for Android connection).

eventually I uninstalled kdeconnect and this solved problem with kdeconnectd obnoxiously listening to tcp/udp.

I do not see any adverse effects.


All times are GMT -5. The time now is 12:31 AM.