xdg-desktop-portal icon indicating copy to clipboard operation
xdg-desktop-portal copied to clipboard

Published 20 hours ago • verified publisher icon flatpak

[Bug]: The background kill watchdog seems too aggressive, killing after 5 seconds

Open kparal opened this issue 2 years ago • 4 comments

Checklist

  • [X] I agree to follow the Code of Conduct that this project adheres to.
  • [X] I have searched the issue tracker for a bug that matches the one I want to file, without success.
  • [X] If this is an issue with a particular app, I have tried filing it in the appropriate issue tracker for the app (e.g. under https://github.com/flathub/) and determined that it is an issue with Flatpak itself.
  • [X] This issue is not a report of a security vulnerability (see here if you need to report a security issue).

Flatpak version

1.15.4

What Linux distribution are you using?

Fedora Linux

Linux distribution version

38

What architecture are you using?

x86_64

How to reproduce

  1. flatpak install flathub com.valvesoftware.Steam
  2. flatpak run com.valvesoftware.Steam
  3. Let it download stuff, then log in, remember credentials. Exit Steam.
  4. flatpak permission-set background background com.valvesoftware.Steam no
  5. flatpak run com.valvesoftware.Steam
  6. See the app stopped abruptly before it can fully start, after cca 5 seconds, without any explanation. Exit code 137.

Expected Behavior

An app should be allowed to start even its startup is slow. There should be some limit, but possibly much longer than 5 seconds.

Actual Behavior

Apps seem to be required to start in < 5 seconds. That feels too aggressive.

Additional Information

See https://github.com/flathub/com.valvesoftware.Steam/issues/1040 . Steam doesn't start for many people, and it took a long time to figure out why.

kparal avatar Apr 25 '23 13:04 kparal

Flatpak isn't the component that does this; moving the issue to xdg-desktop-portal.

smcv avatar Apr 25 '23 13:04 smcv

Slack and yesterday's flatpak release of VSCode are also dying on this issue on my end, setting the background app permission works as a fix.

zr00da avatar Apr 26 '23 16:04 zr00da

It has been quiet a while, any fix for this issue other than background permission workaround ?

SiddharthMant avatar Dec 31 '23 09:12 SiddharthMant

It has been quiet a while, any fix for this issue other than background permission workaround ?

Seemingly removing StartupNotify from the desktop file works around the issue.

AKoskovich avatar Jan 24 '24 21:01 AKoskovich