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

            Bug ID: 514470
           Summary: KDE Connect does not automatically rediscover peers
                    after waking from s2idle (modern standby) until manual
                    user interaction
    Classification: Applications
           Product: kdeconnect
      Version First 23.08.5
       Reported In:
          Platform: Ubuntu
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: desktop-application
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Description

After resuming from suspend using s2idle (modern standby), KDE Connect does not
automatically rediscover peer devices on the local network.
The devices become visible again only after manual user interaction, such as:
- opening KDE Connect settings,
- triggering a refresh,
- a trigger on a neighbor kdeconnect app doesn't have any effect.
This behavior did not occur before enabling aggressive power optimizations, and
does not occur after a cold boot.

Expected behavior

After resuming from suspend (s2idle), KDE Connect should automatically:
- restart its discovery mechanism,
- re-advertise the device,
- rediscover peers without any manual action.

Actual behavior

- After resume from s2idle: KDE Connect daemon is running / Network is up /
Firewall allows traffic
- No passive discovery occurs
- Devices remain invisible indefinitely
- Discovery resumes only after manual UI interaction


Steps to reproduce

1 Boot system normally
2 Verify KDE Connect devices are visible
3 Suspend system: "systemctl suspend"
4 Wake system from s2idle
5 Wait 1–5 minutes
➡️ Result: devices are not rediscovered
➡️ Workaround: open KDE Connect settings or trigger refresh

Tests already performed
✅ NetworkManager reconnects properly
✅ Wi-Fi is active and stable
✅ No wake source issue
✅ Firewall unchanged
✅ Issue reproducible across reboots
❌ systemd system-sleep scripts ineffective
❌ Autostart scripts ineffective
❌ system-level resume hooks ineffective

Conclusion:
➡️ Discovery does not restart automatically at the user-session level

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

Reply via email to