You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simply speaking, who is responsible for deleting the image file and when? The fact that some "black magic" is happening with the document portal does not help.
Some implementations such as xdg-desktop-portal-wlr and xdg-desktop-portal-hyprland are currently using a fixed path (e.g. emersion/xdg-desktop-portal-wlr#298 ). I can only assume that it was done that way because the portal developer was not sure that all clients would remove the file so using a randomized name could lead to a large number of obsolete screenshot files filling up /tmp
Similarly, for a client developed using one of those faulty portal implementations, a developer could observe that the same filename is always reused and so that it should not be bothered to remove it after use.
I suspect that the expected behavior is that the file should be treated like most temporary files:
The portal implementation should randomize the filename to avoid race conditions and possible denials of services.
The client is the sole owner of the file and it is strongly advised to remove it after use to avoid filling up /tmp/
Conclusion: the documentation should be updated to enforce those rules.
Current Behavior
none
Steps to Reproduce
none
Anything else we should know?
No response
The text was updated successfully, but these errors were encountered:
Operating System
any
XDG Desktop Portal version
1.18
XDG Desktop Portal version (Other)
No response
Desktop Environment
Other
Desktop Environment (Other)
No response
Expected Behavior
The current documentation of Screenshot https://flatpak.github.io/xdg-desktop-portal/docs/doc-org.freedesktop.portal.Screenshot.html does not give any details about the ownership and lifetime of the generated image.
Simply speaking, who is responsible for deleting the image file and when? The fact that some "black magic" is happening with the document portal does not help.
Some implementations such as xdg-desktop-portal-wlr and xdg-desktop-portal-hyprland are currently using a fixed path (e.g. emersion/xdg-desktop-portal-wlr#298 ). I can only assume that it was done that way because the portal developer was not sure that all clients would remove the file so using a randomized name could lead to a large number of obsolete screenshot files filling up /tmp
Similarly, for a client developed using one of those faulty portal implementations, a developer could observe that the same filename is always reused and so that it should not be bothered to remove it after use.
I suspect that the expected behavior is that the file should be treated like most temporary files:
Conclusion: the documentation should be updated to enforce those rules.
Current Behavior
none
Steps to Reproduce
none
Anything else we should know?
No response
The text was updated successfully, but these errors were encountered: