Control: severity -1 important Hi Witold,
On Tue, 07 May 2024 02:36:46 +0000 Witold Baryluk <witold.bary...@gmail.com> wrote: [...] > Elevating severity, because it looks like I didn't even installed this > package (I did inspect all apt-get install invokations since system > creation), and it kdeconnect could only be installed due to some > suggests / recommends, not due to any dependency or direct request. How the package was installed on your system, I don't know, but as you suspect it was likely a recommendation of another package. Regarding the issue at hand: I can see why you consider this a problem. But unfortunately, there is no way of changing that behaviour, I suspect the behaviour might be intentional. People have requested this feature upstream (https:// bugs.kde.org/show_bug.cgi?id=432378) and even asked for ways to disable kdeconnectd (https://bugs.kde.org/show_bug.cgi?id=417615). The latter bug report could give you ideas how to achieve that. If this issue poses a serious problem for you, you can remove kdeconnect from your system. That might also give you a hint why it was installed in the first place. Upstream KDE actually recommends installing kdeconnect as part of the Plasma installation. Whether that recommendation fits the Debian's recommendation, is yet to be determined and we might have to see over the recommendation. However, I do disagree about the severity of this. I don't think that this issue warrants the removal of kdeconnect from Debian and hence, I'm lowering it to important. -- Med vänliga hälsningar Patrick Franz