Package Details: kdeconnect-no-mdns 25.12.3-1

Git Clone URL: https://aur.archlinux.org/kdeconnect-no-mdns.git (read-only, click to copy)
Package Base: kdeconnect-no-mdns
Description: Adds communication between KDE and your smartphone. Version without MDNS support, for KDE bug 487719.
Upstream URL: https://kdeconnect.kde.org/
Licenses: GPL-2.0-or-later
Groups: kde-applications, kde-network
Conflicts: kdeconnect
Provides: kdeconnect
Submitter: kelvie
Maintainer: kelvie
Last Packager: kelvie
Votes: 8
Popularity: 0.039584
First Submitted: 2024-05-29 03:19 (UTC)
Last Updated: 2026-03-21 20:44 (UTC)

Required by (13)

Sources (2)

Latest Comments

1 2 Next › Last »

kelvie commented on 2026-03-21 20:47 (UTC)

That's really sad. Anyway I've updated it to the latest version :( Was wondering why I was getting conflicts again.

callegar commented on 2026-03-21 18:23 (UTC)

The old behavior was indeed reverted with https://invent.kde.org/network/kdeconnect-kde/-/commit/09b70658f545a3f37c29cfff75cdb00d2d851fa8 (sigh)

callegar commented on 2026-03-21 17:42 (UTC)

I think that this package is still needed to completely remove mdns from kdeconnect. The newer versions seem to have some autodetection logic that is supposed to determine if there is avahi running or not, but the logic is broken and on an erratic basis I still see kdeconnectd binding to 5353 totally breaking avahi. This is evident from avahi reporting: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***. Killing kdeconnectd and restarting avahi-daemon seems the only way to fix the issue.

kelvie commented on 2025-11-24 23:20 (UTC)

ryan.steed: also saw that in my bug notifications a while back! And thank you for the notification, merged with upstream. Can't wait to drop this PKGBUILD as it is quite a chore.

ryan.steed commented on 2025-11-24 22:46 (UTC)

Thanks for maintaining this package, relief is on the horizon, MDNS is disabled by default in v25.11.80+.

But until then, I'd like to request an upstream security fix:

diff --git a/PKGBUILD b/PKGBUILD
index acc1082..bced3cd 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,7 +8,7 @@ pkgname=kdeconnect-no-mdns
 provides=($_pkgname)
 conflicts=($_pkgname)
 pkgver=25.08.3
-pkgrel=1
+pkgrel=2
 pkgdesc='Adds communication between KDE and your smartphone. Version without MDNS support, for KDE bug 487719.'
 url='https://kdeconnect.kde.org/'
 arch=(x86_64)
@@ -56,13 +56,18 @@ optdepends=('python-nautilus: Nautilus integration'
             'sshfs: remote filesystem browser')
 groups=(kde-applications
         kde-network)
-source=(https://download.kde.org/stable/release-service/$pkgver/src/$_pkgname-kde-$pkgver.tar.xz{,.sig})
+source=(https://download.kde.org/stable/release-service/$pkgver/src/$_pkgname-kde-$pkgver.tar.xz{,.sig}
+        https://invent.kde.org/network/kdeconnect-kde/-/commit/1d757349.patch)
 sha256sums=('6e41f1f22e85f5e70a92dd6ca3e6968364896de37afe5daeb7cda599f03e5e2b'
-            'SKIP')
+            'SKIP'
+            '503ce83b17c7073bd72294e532f95e5d4b74d8894e90e397896ea660b2d4f847')
 validpgpkeys=(CA262C6C83DE4D2FB28A332A3A6A4DB839EAA6D7  # Albert Astals Cid <aacid@kde.org>
               F23275E4BF10AFC1DF6914A6DBD2CE893E2D1C87  # Christoph Feck <cfeck@kde.org>
               D81C0CB38EB725EF6691C385BB463350D6EF31EF) # Heiko Becker <heiko.becker@kde.org>

+prepare() {
+  patch -d $_pkgname-kde-$pkgver -p1 < 1d757349.patch # CVE fix
+}

 build() {
   cmake -B build -S $_pkgname-kde-$pkgver \

kelvie commented on 2025-10-12 22:29 (UTC)

Thanks @ufo_driver! I've added it to my reader/notifications.

ufo_driver commented on 2025-10-12 20:06 (UTC)

@kelvie you can use this Atom in your RSS reader: https://invent.kde.org/network/kdeconnect-kde/-/tags?format=atom

This way you will be notified immediately by their GitLab.

kelvie commented on 2025-07-04 05:28 (UTC)

Thank you to whoever keeps sending the out-of-date notifications. I actually have an rss reader set up to look for updates, but whenever KDE releases, there are way too many entries in the arch RSS feed for me to get notified that this is out of date automatically.

Anyone else know how else I can get notified that there's a new version without relying on someone to ping me here?

kelvie commented on 2025-04-13 04:45 (UTC)

I have no idea how it got to .4, possibly a merge conflict blooper.

Poscat commented on 2025-04-13 04:02 (UTC)

Did you forgot to commit PKGBUILD?

1 2 Next › Last »