You are not logged in.
Hi there this seems to be a change in a resent update, I get the error "Discover Is Offline" when opening even though its clearly showing flatpaks and is online.
I use hyprland on base arch, however I use systemd-networkd on a cabled connection, I also have bridged networking for VMs.
I also have a static address set, systemd-resolved is is running and /etc/resolv.conf is linked to /run/systemd/resolve/resolv.conf and is showing my DNS server correctly.
discover is version 6.7.5-1
I do have networkmanager installed even though the service is disabled & masked (dbus kept starting it and breaking my network bridge)
I do have plasma installed as a backup but I can't actualy remember the last time I used it.
and I only have one flatpak installed, so this isn't urgent, and to be blunt clicking "ok" on an error I'm not going to see very often isn't a problem.
I'm just curious if anyone else has noticed this issue, and if there is a quick fix that isn't too much of a bodge. I'm not going to loose sleep if there isn't,
Many thanks in advance
● systemd-networkd.service - Network Management
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service>
Active: active (running) since Sun 2026-10-11 21:51:16 BST; 45mi>
Invocation: 09328feba1f449fc9203be7f7663b708
TriggeredBy: ● systemd-networkd-varlink-metrics.socket
● systemd-networkd.socket
● systemd-networkd-varlink.socket
● systemd-networkd-resolve-hook.socket
Docs: man:systemd-networkd.service(8)
man:org.freedesktop.network1(5)
Main PID: 428 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 76903)
FD Store: 0 (limit: 512)
Memory: 4.2M (peak: 6.8M)
CPU: 84ms
CGroup: /system.slice/systemd-networkd.service
└─428 /usr/lib/systemd/systemd-networkd
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service>
Active: active (running) since Sun 2026-10-11 21:51:16 BST; 47mi>
Invocation: 0af50b1ae01640ed944d5630a8b5108b
TriggeredBy: ● systemd-resolved-varlink.socket
● systemd-resolved-monitor.socket
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://systemd.io/WRITING_NETWORK_CONF … N_MANAGERS
https://systemd.io/WRITING_RESOLVER_CLIENTS
Main PID: 419 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 76903)
Memory: 2.9M (peak: 4M)
CPU: 286ms
CGroup: /system.slice/systemd-resolved.service
└─419 /usr/lib/systemd/systemd-resolved
○ NetworkManager.service
Loaded: masked (Reason: Unit NetworkManager.service is masked.)
Active: inactive (dead)
Offline