| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
This kludge is no longer necessary with the bus TrackerSparqlConnection
implementing get_namespace_manager(). We can ask the connection being
forwarded about its own namespaces now.
|
|
|
|
|
| |
This is redundant, and Fedora has made it a requirement to drop
unnecessary rpaths.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Coverity complains here, even though there's no paths that inner_error
is set but not used. Mark it as autoptr, so it's more consistent and
makes Coverity shut up here.
CID: #1501149
|
|
|
|
|
|
|
|
|
| |
We don't make it look like we are declaring an array, so the compiler
thinks the { NULL } is actually the declaration of the GStrv itself.
We do want a pointer to an empty GStrv instead, so make it clear that
this is a string array.
CID: #1501141
|
|
|
|
|
|
|
| |
This variable is already g_autoptr, no need to free it in the
error paths.
CID: #1501111
|
|
|
|
|
|
|
|
|
| |
We get fully expanded graph names from TrackerNotifier events, but
we allow prefixed names in flatpak rules. Expand the latter so we
match both, as a last resort.
This fixes propagation of changes from these graphs to the sandboxed
applications.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The portal is currently first claiming the bus name, then adding
the portal object+interface. This may break things with autostart
as clients are able to send a message to an object path that is not
there yet.
Changing the order means the object path is there when the DBus name
is made known, so clients are able to talk immediately to it.
Fixes the error reported at
https://github.com/flathub/org.gnome.Music/pull/24#issuecomment-702565846
|
|
|
|
| |
Otherwise we try to error out, but never really finish the DBus invocation.
|
|
|
|
|
|
| |
This will be used by our functional test suite to test portal workings.
Likewise, use this envvar presence to force the use of the Tracker portal
in the bus TrackerSparqlConnection.
|
|
|
|
| |
We used to get this from tracker_sparql_dep, that will change.
|
|
|
|
|
| |
So it is not necessary to use the full IRI in order to specify a graph
in a flatpak build specification file.
|
|
|
|
|
|
|
|
|
| |
If the service URI we are asking permissions for has the default
object path, ensure we look it up with it being implicitly defined.
This allows the following policies to work the same:
dbus:org.example.Endpoint=*
dbus:org.example.Endpoint:/org/freedesktop/Tracker1/Endpoint=*
|
|
|
|
|
|
|
|
|
|
| |
The helper function may return NULL keyfile and no error if the
.flatpak-info file does not exist.
If that is the case, there is good chance we are talking with a
client outside a sandbox. Still be overly restrictive and allow
access to an empty set of graphs, the client shouldn't be talking
to the portal in that case.
|
| |
|
|
|
|
|
|
| |
This request takes an object path received through CreateSession,
checks ownership from the DBus sender, and explicitly closes a
session.
|
|
|
|
| |
So the service can be autostarted
|
|
|
|
| |
And close sessions when those vanish
|
|
|
|
|
| |
Those translate to CONSTRAINT GRAPH ALL and CONSTRAINT GRAPH DEFAULT,
to let access to all graphs, or the default unnamed graph specifically.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This endpoint is a private subclass that manipulates communication
so
1) session endpoints can only be used by their original creator
2) all update queries are forbidden
3) GraphUpdated filters down events on disallowed graphs
4) Queries are prepended CONSTRAINT clauses
This makes sandboxed endpoints restricted so:
- Updates cannot happen
- Graphs/Services in queries get filtered down
- GraphUpdated signals avoid filtered down graphs
|
|
|