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

            Bug ID: 517457
           Summary: Flatpak notifications and inhibitions fail after
                    system resume (Plasma 6.3)
    Classification: Plasma
           Product: xdg-desktop-portal-kde
      Version First git-stable-Plasma/6.3
       Reported In:
          Platform: Debian stable
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

SUMMARY
Flatpak applications (such as the Francis Pomodoro timer) lose the ability to
send notifications or manage power inhibitions after the system resumes from a
suspend state (suspend-to-RAM). The xdg-desktop-portal-kde service fails to
process D-Bus calls related to these functions after resume, effectively
silencing Flatpak apps until the portal services are manually restarted.


STEPS TO REPRODUCE
   1. Open a Flatpak application that relies on notifications or power
inhibition (e.g., Francis).
   2. Start an action that triggers a notification (like a timer).
   3. Suspend the computer and then Resume it.
   4. Wait for the application to trigger its notification.


OBSERVED RESULT
No notification popup appears and no sound is played. The application continues
to run but stays "silent." System logs show QDBusConnection errors: couldn't
handle call to CreateMonitor, no slot matched and Could not find slot
InhibitPortal::CreateMonitor.


EXPECTED RESULT
The notification should be displayed correctly on the screen and play the
notification sound immediately after the application triggers it, regardless of
the system power state history.


SOFTWARE/OS VERSIONS
   * Linux/KDE Plasma: Debian GNU/Linux 13 (Stable)
   * KDE Plasma Version: 6.3.6
   * KDE Frameworks Version: 6.13.0
   * Qt Version: 6.8.2
   * Kernel Version: 6.12.73+deb13-amd64 (64-bit)
   * Graphics Platform: X11

ADDITIONAL INFORMATION
The issue is temporarily fixed by restarting the portal services:
systemctl --user restart xdg-desktop-portal-kde xdg-desktop-portal
This confirms the failure is in the portal backend communication after the
power state change.

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

Reply via email to