Update to KDE 6 broke Network Services in Dolphin (KDNSSD error)

Hi everyone!

The upgrade to KDE 6.0.3 (from KDE 5) has destroyed my network environment in the Dolphin file manager.

Before I could access my NAS via Samba.
Now I get the error message “The KDNSSD library has been built without Zeroconf support.” when I click on “Network Services”.

Is there a way to (re-)install the required bundles?

Current workaround:
Use GNOME filemanager for networkdrives
Downgrade to version 41230 did not work.

Details:
Operating System: Clear Linux OS 41450
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.4-1422.native (64-bit)
Graphics Platform: Wayland

Ah yes thanks for the report - I can see this in the build logs

fixing this for the next release

1 Like

After updating to the latest version 41540, the situation has unfortunately become worse for KDE.

There is no automatic login on boot.
There is only a “_” at the top left and the mouse pointer in the middle of a black screen.

Workaround:
Open console: CTL+ALT+F3
login
Type: startplasma-wayland

After starting Dolphin there is now a new error message:
The Zeroconf daemon (mdnsd) is not running.

Yep, me too regarding sddm not launching. I opened a bug report.

Yup, same problem here.

the sddm thing hopefully is resolved in the current in-progress release … so if all goes well, small number of hours before it goes live

1 Like

Update to Clear Linux OS 41560

  • fixed the autologin/sddm problem.
  • Zeroconf daemon error still existing

Update to Clear Linux OS 41610

  • Zeroconf daemon error still existing

KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.3
Kernel Version: 6.8.7-1429.native (64-bit)
Graphics Platform: Wayland

Update to Clear Linux OS 41640

  • Zeroconf daemon error still existing

Is this the correct place to report bugs or would it be better placed elsewhere?


KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.3
Kernel Version: 6.8.8-1430.native (64-bit)
Graphics Platform: Wayland

Is avahi installed/enabled on that system?

Alternatively were you using systemd-resolved mdns?

This is what I tried:

  • avahi-daemon is installed
  • but service fails to start
  • “No NSS support for mDNS detected” & “Failed to contact D-Bus daemon”
  • but dbus.service is running and systemd-resolve lists +mDNS under Protocols

Details:

user@user-pc~ $ sudo swupd bundle-list | grep avahi
Passwort: 
 - avahi-daemon
user@user-pc~ $ sudo systemctl status avahi-daemon
× avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2024-05-02 19:01:20 CEST; 4min 10s ago
TriggeredBy: ● avahi-daemon.socket
    Process: 10030 ExecStart=/usr/bin/avahi-daemon -s (code=exited, status=255/EXCEPTION)
   Main PID: 10030 (code=exited, status=255/EXCEPTION)
     Status: "avahi-daemon 0.8 exiting."

Mai 02 19:01:20 user-pc avahi-daemon[10030]: Found user 'avahi' (UID 350) and group 'avahi' (GID 350).
Mai 02 19:01:20 user-pc avahi-daemon[10030]: Successfully dropped root privileges.
Mai 02 19:01:20 user-pc avahi-daemon[10030]: avahi-daemon 0.8 starting up.
Mai 02 19:01:20 user-pc avahi-daemon[10030]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mai 02 19:01:20 user-pc avahi-daemon[10030]: dbus_bus_request_name(): Connection ":1.350" is not allowed to own the service "org.freedesktop.Avahi" due >
Mai 02 19:01:20 user-pc avahi-daemon[10030]: WARNING: Failed to contact D-Bus daemon.
Mai 02 19:01:20 user-pc avahi-daemon[10030]: avahi-daemon 0.8 exiting.
Mai 02 19:01:20 user-pc systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/EXCEPTION
Mai 02 19:01:20 user-pc systemd[1]: avahi-daemon.service: Failed with result 'exit-code'.
Mai 02 19:01:20 user-pc systemd[1]: Failed to start avahi-daemon.service.
user@user-pc~ $ sudo swupd search nss-mdns
Search failed, no reasonable results found
user@user-pc~ $ sudo swupd search nss
Bundle with the best search result:
     devpkg-nss                         - All content for pkgconfig file nss.pc. 

This bundle can be installed with:

  swupd bundle-add  devpkg-nss

Alternative bundle options are
     games                              - Play games in Clear Linux OS. 
     cryptography                       - Encrypt, decrypt, sign and verify objects. 
     enterprise-login                   - Enable enterprise login systems like Active Directory. 
user@user-pc~ $ sudo swupd search mdns
Search failed, no reasonable results found
user@user-pc~ $ systemctl status dbus
● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
     Active: active (running) since Thu 2024-05-02 18:54:09 CEST; 13min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 580 (dbus-daemon)
      Tasks: 1 (limit: 38328)
     Memory: 5.1M ()
     CGroup: /system.slice/dbus.service
             └─580 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
user@user-pc~ $ sudo systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; preset: disabled)
     Active: active (running) since Thu 2024-05-02 18:54:09 CEST; 17min ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 523 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 38328)
     Memory: 5.5M ()
     CGroup: /system.slice/systemd-resolved.service
             └─523 /usr/lib/systemd/systemd-resolved

Mai 02 18:54:16 user-pc systemd-resolved[523]: wlp6s0: Bus client set search domain list to: fritz.box
Mai 02 18:54:16 user-pc systemd-resolved[523]: wlp6s0: Bus client set default route setting: yes
Mai 02 18:54:16 user-pc systemd-resolved[523]: wlp6s0: Bus client set DNS server list to: 192.168.178.1
Mai 02 18:54:16 user-pc systemd-resolved[523]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.178.1.
Mai 02 18:54:21 user-pc systemd-resolved[523]: wlp6s0: Bus client set DNS server list to: 192.168.178.1, fd00::de39:6fff:fe11:966, 2a02:1748:dd5e:4060:d>
Mai 02 18:54:41 user-pc systemd-resolved[523]: Clock change detected. Flushing caches.
Mai 02 18:54:46 user-pc systemd-resolved[523]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server fd00::de39:6fff:fe11:966.
Mai 02 19:01:19 user-pc systemd-resolved[523]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 2a02:1748:dd5e:4060:de39:6fff:fe11:966.
Mai 02 19:02:58 user-pc systemd-resolved[523]: Grace period over, resuming full feature set (UDP+EDNS0) for DNS server 192.168.178.1.
Mai 02 19:02:58 user-pc systemd-resolved[523]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.178.1.
user@user-pc~ $ systemd-resolve --status | grep -i mdns
           Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
         Protocols: -DefaultRoute -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    Current Scopes: DNS mDNS/IPv4 mDNS/IPv6
         Protocols: +DefaultRoute -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported

In the newest version it changes back to the original error message: