| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| notification-Don-t-expect-to-fail-requests-with-unsupport.patch | notification: Don't expect to fail requests with unsupported properties libportal 0.9.0 filters unsupported properties from a notification request without failing it. [smcv: Separated from a larger commit] |
Julian Sparber <julian@sparber.net> | no | debian | upstream, 1.19.0, part of commit:bf29961854a2b8a6dee3f054aa0fd16a6a66486c | 2024-01-17 |
| Add-missing-entry-to-NEWS-file.patch | Add missing entry to NEWS file | Georges Basile Stavracas Neto <georges.stavracas@gmail.com> | no | upstream, 1.18.5, commit:c80cb5ca36f3fdc67ed8538496a72078f481111d | 2024-04-18 | |
| Camera-use-an-empty-app-id-for-host-apps.patch | Camera: use an empty app id for host apps Sending an app id that doesn't resolve to valid app info (e.g. a desktop file is not found) will automatically reject camera request, because the backend is not able to verify whether the app (based on app id) runs in the background. Same will happen if the app id resolves to an app where our app was started from. This happens for example when you start apps in GNOME using Alt + F2, where we get invalid app id from cgroups and since it doesn't find opened application window for this app, it will automatically reject the request. Using an empty id fixes this problem. (cherry picked from commit 6cd99b04d438b1de9b25c7bd928e541609904db3) |
Jan Grulich <grulja@gmail.com> | no | upstream, 1.18.5, commit:45b5f7a47af4f23cb2db26f2bb03ecaf4db7349d | 2024-11-12 | |
| tests-notification-Check-result-in-notification-add-callb.patch | tests/notification: Check result in notification add callback Adding a notification may fail, instead of waiting for the timeout we can check the result we get in the callback. |
Julian Sparber <julian@sparber.net> | no | upstream, 1.19.0, commit:8224047c11c5b77d43901764b5f085f7a717e26f | 2024-02-29 | |
| tests-notification-Report-backend-errors.patch | tests/notification: Report backend errors For debugging it's important that the backend doesn't just crash without telling the reason. It would be even nicer if the test would fail immediately instead of hitting the timeout, but that' currently not possible since the client doesn't know whether the backend failed. |
Julian Sparber <julian@sparber.net> | no | upstream, 1.19.0, commit:fdd9759e06420e74cadae17de0e8016a99e8aea1 | 2024-04-05 | |
| tests-notification-Remove-redundant-code.patch | tests/notification: Remove redundant code We can reuse most of the test setup for all tests. This will make it easier to test more properties. |
Julian Sparber <julian@sparber.net> | no | upstream, 1.19.0, commit:ef84dcdd3f761d3fee6ae43b8be0ac4d8d165e50 | 2024-03-22 |