https://bugs.kde.org/show_bug.cgi?id=526981

            Bug ID: 526981
           Summary: Discover shows "Discover is offline" when using
                    systemd-networkd even though it is clearly online and
                    can install flatpaks
    Classification: Applications
           Product: Discover
      Version First 6.7.5
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: discover
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

DESCRIPTION
Discover shows "Discover is offline" when using systemd-networkd even though it
is clearly online and can Install flatpaks

STEPS TO REPRODUCE
My system is running base arch with plasma installed, I use systemd-networkd as
I have a cabled connection with a static address, and bridged for virtual
machines.  

OBSERVED RESULT
Popup window with a yellow exclamaition mark, the title is "Dicsover is
Offline" and the text is "please connect to a network to install applications
and update the system."

I do still get a list of applications (Flatpaks) and can install as nomal.

EXPECTED RESULT
Exactly the same as above without the network warning, 

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.12.0
Kernel Version: 7.2.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i7-5960X CPU @ 3.00GHz
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 580 Series

ADDITIONAL INFORMATION
This error is new and reproducable on a clean VM, and only since I last updated
sudo pacman -Syu

● 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)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to