Flags

No flags.

Application opens in a terminal window.

Application supports URI arguments.

Application supports startup notification. Since 2.26

Catch-all for unknown values

Default. Deprecated in 2.74, use ApplicationFlagsDefaultFlags instead

Default flags. Since: 2.74

Run as a service. In this mode, registration fails if the service is already running, and the application will initially wait up to 10 seconds for an initial activation message to arrive.

Don't try to become the primary instance.

This application handles opening files (in the primary instance). Note that this flag only affects the default implementation of local_command_line(), and has no effect if ApplicationFlagsHandlesCommandLine is given. See applicationRun for details.

This application handles command line arguments (in the primary instance). Note that this flag only affect the default implementation of local_command_line(). See applicationRun for details.

Send the environment of the launching process to the primary instance. Set this flag if your application is expected to behave differently depending on certain environment variables. For instance, an editor might be expected to use the GIT_COMMITTER_NAME environment variable when editing a git commit message. The environment is available to the Application::commandLine signal handler, via applicationCommandLineGetenv.

Make no attempts to do any of the typical single-instance application negotiation, even if the application ID is given. The application neither attempts to become the owner of the application ID nor does it check if an existing owner already exists. Everything occurs in the local process. Since: 2.30.

Allow users to override the application ID from the command line with --gapplication-app-id. Since: 2.48

Allow another instance to take over the bus name. Since: 2.60

Take over from another instance. This flag is usually set by passing --gapplication-replace on the commandline. Since: 2.60

Catch-all for unknown values

operation requires a password.

operation requires a username.

operation requires a domain.

operation supports saving settings.

operation supports anonymous users.

operation takes TCRYPT parameters (Since: 2.58)

Catch-all for unknown values

No flags set.

Allow another message bus connection to claim the name.

If another message bus connection owns the name and have specified BusNameOwnerFlagsAllowReplacement, then take the name from the other connection.

If another message bus connection owns the name, immediately return an error from g_bus_own_name() rather than entering the waiting queue for that name. (Since 2.54)

Catch-all for unknown values

No flags set.

If no-one owns the name when beginning to watch the name, ask the bus to launch an owner for the name.

Catch-all for unknown values

No flags.

At end of input data

Flush data

Catch-all for unknown values

No flags set.

The bus must not launch an owner for the destination name in response to this method invocation.

the caller is prepared to wait for interactive authorization. Since 2.46.

Catch-all for unknown values

No flags set.

The connection supports exchanging UNIX file descriptors with the remote peer.

Catch-all for unknown values

No flags set.

Perform authentication against server.

Perform authentication against client.

When authenticating as a server, allow the anonymous authentication method.

Pass this flag if connecting to a peer that is a message bus. This means that the Hello() method will be invoked as part of the connection setup.

If set, processing of D-Bus messages is delayed until dBusConnectionStartMessageProcessing is called.

When authenticating as a server, require the UID of the peer to be the same as the UID of the server. (Since: 2.68)

When authenticating, try to use protocols that work across a Linux user namespace boundary, even if this reduces interoperability with older D-Bus implementations. This currently affects client-side EXTERNAL authentication, for which this flag makes connections to a server in another user namespace succeed, but causes a deadlock when connecting to a GDBus server older than 2.73.3. Since: 2.74

Catch-all for unknown values

No flags set.

Each method invocation is handled in a thread dedicated to the invocation. This means that the method implementation can use blocking IO without blocking any other part of the process. It also means that the method implementation must use locking to access data structures used by other threads.

Catch-all for unknown values

No flags set.

A reply is not expected.

The bus must not launch an owner for the destination name in response to this message.

If set on a method call, this flag means that the caller is prepared to wait for interactive authorization. Since 2.46.

Catch-all for unknown values

No flags set.

If not set and the manager is for a well-known name, then request the bus to launch an owner for the name if no-one owns the name. This flag can only be used in managers for well-known names.

Catch-all for unknown values

No flags set.

Property is readable.

Property is writable.

Catch-all for unknown values

No flags set.

Don't load properties.

Don't connect to signals on the remote object.

If the proxy is for a well-known name, do not ask the bus to launch an owner during proxy initialization or a method call. This flag is only meaningful in proxies for well-known names.

If set, the property value for any invalidated property will be (asynchronously) retrieved upon receiving the `PropertiesChanged` D-Bus signal and the property will not cause emission of the DBusProxy::gPropertiesChanged signal. When the value is received the DBusProxy::gPropertiesChanged signal is emitted for the property along with the retrieved value. Since 2.32.

If the proxy is for a well-known name, do not ask the bus to launch an owner during proxy initialization, but allow it to be autostarted by a method call. This flag is only meaningful in proxies for well-known names, and only if DBusProxyFlagsDoNotAutoStart is not also specified.

Don't actually send the AddMatch D-Bus call for this signal subscription. This gives you more control over which match rules you add (but you must add them manually). (Since: 2.72)

Catch-all for unknown values

No flags set.

Do not automatically assign a serial number from the DBusConnection object when sending a message.

Catch-all for unknown values

No flags set.

All DBusServer::newConnection signals will run in separated dedicated threads (see signal for details).

Allow the anonymous authentication method.

Require the UID of the peer to be the same as the UID of the server when authenticating. (Since: 2.68)

Catch-all for unknown values

No flags set.

Don't actually send the AddMatch D-Bus call for this signal subscription. This gives you more control over which match rules you add (but you must add them manually).

Match first arguments that contain a bus or interface name with the given namespace.

Match first arguments that contain an object path that is either equivalent to the given path, or one of the paths is a subpath of the other.

Catch-all for unknown values

No flags set.

Method calls to objects not in the enumerated range will still be dispatched. This is useful if you want to dynamically spawn objects in the subtree.

Catch-all for unknown values

No flags set.

Catch-all for unknown values

no flags set.

copy the attribute values when the file is copied.

copy the attribute values when the file is moved.

Catch-all for unknown values

No flags set.

Overwrite any existing files

Make a backup of any existing files.

Don't follow symlinks.

Copy all file metadata instead of just default set used for copy (see FileInfo).

Don't use copy and delete fallback if native move not supported.

Leaves target file with default perms, instead of setting the source file perms.

Catch-all for unknown values

No flags set.

Create a file that can only be accessed by the current user.

Replace the destination as if it didn't exist before. Don't try to keep any old permissions, replace instead of following links. This is generally useful if you're doing a "copy over" rather than a "save new version of" replace operation. You can think of it as "unlink destination" before writing to it, although the implementation may not be exactly like that. This flag can only be used with fileReplace and its variants, including fileReplaceContents. Since 2.20

Catch-all for unknown values

No flags set.

Report any error encountered while traversing the directory tree. Normally errors are only reported for the toplevel file.

Tally usage based on apparent file sizes. Normally, the block-size is used, if available, as this is a more accurate representation of disk space used. Compare with du --apparent-size.

Do not cross mount point boundaries. Compare with du -x.

Catch-all for unknown values

No flags set.

Watch for mount events.

Pair DELETED and CREATED events caused by file renames (moves) and send a single G_FILE_MONITOR_EVENT_MOVED event instead (NB: not supported on all backends; the default behaviour -without specifying this flag- is to send single DELETED and CREATED events). Deprecated since 2.46: use FileMonitorFlagsWatchMoves instead.

Watch for changes to the file made via another hard link. Since 2.36.

Watch for rename operations on a monitored directory. This causes FileMonitorEventRenamed, FileMonitorEventMovedIn and FileMonitorEventMovedOut events to be emitted when possible. Since: 2.46.

Catch-all for unknown values