[Bug 1871030] Re: There's no Option to Disable the Startup of KDEConnect

2022-05-13 Thread Marcus Sundman
Nothing should just respawn failing processes continuously within a
short span of time. Once the kdeconnect service crashes, what is causing
it to launch again immediately? Whatever it is needs to be smarter about
things, to avoid respawning the same crashing service millions, or even
hundreds, of times per hour.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030]

2022-05-13 Thread Forest
Alternative workaround step 2, leaving system config files untouched:

Copy /usr/share/dbus-1/services/org.kde.kdeconnect.service to
~/.local/share/dbus-1/services/ and change the Exec= line of the copy to
Exec=/usr/bin/false

When combined with step 1 of my workaround, this prevents kdeconnectd
from launching in that user's sessions. It adds some clutter to the
session log, as dbus-daemon complains that the executable is failing,
but it gives up after several tries and seems to remain quiet after
that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030]

2022-04-15 Thread Forest
I found some (ugly) workarounds for the unwanted kdeconnectd autostart.

The process seems to be launched at session startup time from two
distinct places:

1. /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop

This can be disabled for individual users by copying the file to each
user's ~/.config/autostart/ directory and adding Hidden=true to the
[Desktop Entry] section of the copies.

Alternatively, it can be disabled by default by adding a line like this to the 
file's [Desktop Entry] section:
  X-KDE-autostart-condition=kdeconnectd-autostartrc:General:Autostart:false
Then, to re-enable it for a particular user, create a 
~/.config/kdeconnectd-autostartrc file with Autostart=true in its [General] 
section. (The file name "kdeconnectd-autostartrc" is arbitrary; I chose it in 
hopes of avoiding conflicts with any standard files.)

2. /usr/share/dbus-1/services/org.kde.kdeconnect.service

According to KDE docs*, this file tells every user's dbus session to launch 
kdeconnectd if something tries to contact it over d-bus. With this file in 
place, kdeconnectd is launched by systemd at session start even if a user 
disables the autostart .desktop file. The file can be moved to a backup 
directory to avoid this. However, I think a better fix would be to identify 
whatever is making org.kde.kdeconnect d-bus requests at session startup, and 
prevent that instead.
* https://develop.kde.org/docs/use/d-bus/dbus_autostart_services/

Of course, these workarounds are hackish, and will probably revert to
the normal (unwanted) behavior whenever KDE Connect package updates are
installed. What we really need is for it to be configurable in the first
place. Seems like a good fit for the Background Services panel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030]

2022-02-27 Thread Forest
> unable to communicate with the first paired instance

The word "paired" should have been in parentheses. I don't know what ate
them. To be clear, only one user has paired KDE Connect with the Android
app, yet the second user's kdeconnectd instance makes the first instance
stop working. Unless there's another way to fix this, I think I need a
way to disable kdeconnectd for the second user.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030]

2022-02-27 Thread Forest
+1 for adding the option on a per-user basis. It's not just a matter of
convenience; the lack of this option breaks KDE Connect on my multiuser
system: As soon as a second desktop session is started, the new
kdeconnectd instance seems to steal the Android app's attention, leaving
it unable to communicate with the first paired instance.

I tried copying /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop to
the second user's ~/.config/autostart/ and adding Hidden=true, as
specified in the freedesktop spec. It didn't help.

I tried renaming /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop.
It didn't help.

I searched for a systemd --user unit that I could disable. I didn't find
one.

This really should be a per-user option, listed in Background Services
along with all the others.

In the meantime, I would appreciate a workaround, if somebody knows of
one.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030]

2021-01-23 Thread Mitchnull
The open port is indeed an attack surface, there should be an option to
run kdeconnect only when needed.

Kdeconnect should be visible among the auto-run services so that it
could be disabled (without uninstalling).

Additionally it would be nice to have an option to disable just the
listening socket from the system tray menu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030]

2020-12-16 Thread Physkets
Yes, KDEConnect in no way counts as essential. Can the 'No Display'
aspect be removed?

An option to disable it is even more essential in light of this recent issue:
https://kde.org/info/security/advisory-20201002-1.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030] Re: There's no Option to Disable the Startup of KDEConnect

2020-10-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: kdeconnect (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030]

2020-04-07 Thread 5-kde
Other than listing all Running Processes, is there a way to see an
unabridged (and exclusive) list of all auto-start applications that are
running as "NoDisplay"?

Your point of preventing users from "shooting themselves in the foot"
makes sense, but on the other hand, transparency is also important. I
like your idea of labeling important things as essential services. But
in my case, KDEConnect is not an essential service.

I think it is ok to warn people before allowing them to toggle something
important off, but "hiding it completely" seems less than forthcoming.
The policy I'd advocate, is that if a program or service is important
enough to auto-start, it is important enough to be listed in an
unabridged list where all other auto-start programs and service are
listed. Such lists should be unabridged in my opinion. If it auto-
starts, list it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871030] Re: There's no Option to Disable the Startup of KDEConnect

2020-04-06 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=417615.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2020-02-14T07:16:21+00:00 Tagwerk19 wrote:

SUMMARY:

Seems to be no way of disabling kdeconnect (so that the kdeconnectd
process is not running)

STEPS TO REPRODUCE:

1. Look in "System Settings", "KDE Connect" for an option to disable
the service.

2. ... then try "System Settings", "Startup and Shutdown",
"Background Services"

EXPECTED RESULTS:

A "Enable KDE Connect" option that can be unchecked...

DESIRED RESULT:

An option that is not checked until you decide to...

SOFTWARE/OS VERSIONS:

System Settings 5.18.0
kdeconnect 1.4 (?)
from Neon Testing

KDE Plasma 5.18.0
KDE Frameworks 5.68.0
Qt 5.13.2 

ADDITIONAL INFORMATION:

There's an option in System Settings "File Search" to enable or
disable search. Looking for an equivalent option for kdeconnect

Request triggered by a discussion that the "slow start for gwenview"
might be related to running kdeconnect (Bug 411196)

Looks like not all distributions have KDEconnect installed by
default, seemingly Fedora does not, Neon does. In the case that it is
installed, there should be an easily discoverable way of controlling it
and maybe it should not be active by default. There's the principle that
if a service is not needed it should not be running by default (all the
more so when it has an open port)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030/comments/0


On 2020-02-14T21:30:38+00:00 Matthijstijink-k wrote:

You can just uninstall it, if it's not needed.

Otherwise, I _think_ you can disable it by removing the plasmoid, and
overriding the XDG autostart (see
https://wiki.archlinux.org/index.php/XDG_Autostart).


I am going to leave this bug open though, since having such an option could be 
useful in some cases (e.g. multi-user systems).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030/comments/1


On 2020-02-15T08:57:58+00:00 Tagwerk19 wrote:

Tried creating a

.config/autostart/org.kde.kdeconnect.daemon.desktop

file (0744), containing

[Desktop Entry]
Hidden=True

The kdeconnectd process was still here. More magic seemily required.

Uninstall works (without taking out other apps/libraries).

"Wishlist" is fine; heads up though that there a process with an open
port (seemingly just IPv6...)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030/comments/2


On 2020-02-20T10:38:23+00:00 Tagwerk19 wrote:

For what it's worth, the "IPv6 only" comment above came from a
misunderstanding of the netstat output. If it lists a service listening
on "tcp6", it is _also_ listening on IPv4. Confirmation by:

root@testbox:~# nc -v 127.0.0.1 1716
Connection to 127.0.0.1 1716 port [tcp/*] succeeded!
^C

root@testbox:~# pkill kdeconnectd

root@testbox:~# nc -v 127.0.0.1 1716
nc: connect to 127.0.0.1 port 1716 (tcp) failed: Connection refused

So, the KDE Connect has an open port on both IPv4 and IPv6

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030/comments/3


On 2020-04-06T07:15:31+00:00 5-kde wrote:

What is so special about KDEConnect, that it can run each time I boot my
computer and not show itself (officially) here: Settings > Startup and
Shutdown > Background Services > Startup Services?

This may be a great application, but it should hide itself as a
preference; there needs to be a way to toggle it on and off without
uninstalling it.

I submitted a downstream bug report regarding this matter here:
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030/comments/6


On 2020-04-06T07:26:07+00:00 5-kde wrote:

Not listed:
https://i.stack.imgur.com/FtRl2.jpg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030/comments/7


On 2020-04-06T07:39:52+00:00 8p-k26-gj wrote:

KDE Connect is a regular autostart applications. It is marked as "NoDisplay", 
though.
I was wondering if the Autostart KCM should display such

[Bug 1871030] Re: There's no Option to Disable the Startup of KDEConnect

2020-04-06 Thread Lonnie Lee Best
** Bug watch added: KDE Bug Tracking System #417615
   https://bugs.kde.org/show_bug.cgi?id=417615

** Also affects: kdeconnect-desktop via
   https://bugs.kde.org/show_bug.cgi?id=417615
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdeconnect in Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1871030] [NEW] There's no Option to Disable the Startup of KDEConnect

2020-04-06 Thread Lonnie Lee Best
Public bug reported:

In Kubuntu 19.10 (and likely Kubuntu 20.04), why is KDEConnect not listed as a 
Background Service here?:
https://i.stack.imgur.com/FtRl2.jpg

Run this command in Kubuntu 19.10:
lsof -i

You'll see that KDEConnect is listening on UDP 1716 and TCP 1716.

I want to prevent KDEConnect from running each time I reboot my
computer, because I do not use this service and I do not appreciate
unused services that run each time my computer starts (especially ones
that hide themselves from official lists like that of Startup Services
-- screenshot linked above).

What is so special about KDEConnect that it should run all the time,
whether you need it or not (and without the GUI-level-ability to toggle
it off)?

Is this something that can be addressed before Kubuntu 20.04 is
released?

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: kdeconnect 1.3.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Apr  6 01:52:24 2020
InstallationDate: Installed on 2020-02-03 (62 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: kdeconnect
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kdeconnect (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871030

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs