Gio.DebugController¶

Implementations:: Gio.DebugControllerDBus

Methods¶

	`get_debug_enabled` ()
	`set_debug_enabled` (debug_enabled)

Virtual Methods¶

None

Properties¶

Name	Type	Flags	Short Description
`debug-enabled`	`bool`	r/w/en	Whether to expose debug output

Signals¶

None

Fields¶

None

Class Details¶

class Gio.DebugController¶

Bases:: GObject.GInterface
Structure:: Gio.DebugControllerInterface

Gio.DebugController is an interface to expose control of debugging features and debug output.

It is implemented on Linux using Gio.DebugControllerDBus, which exposes a D-Bus interface to allow authenticated peers to control debug features in this process.

Whether debug output is enabled is exposed as Gio.DebugController :debug-enabled. This controls GLib.log_set_debug_enabled() by default. Application code may connect to the GObject.Object ::notify signal for it to control other parts of its debug infrastructure as necessary.

If your application or service is using the default GLib log writer function, creating one of the built-in implementations of Gio.DebugController should be all that’s needed to dynamically enable or disable debug output.

New in version 2.72.

get_debug_enabled()[source]¶

Returns:: True if debug output should be exposed, False otherwise
Return type:: bool

Get the value of Gio.DebugController :debug-enabled.

New in version 2.72.

set_debug_enabled(debug_enabled)[source]¶

Parameters:: debug_enabled (bool) – True if debug output should be exposed, False otherwise

Set the value of Gio.DebugController :debug-enabled.

New in version 2.72.

Property Details¶

Gio.DebugController.props.debug_enabled¶

Name:: debug-enabled
Type:: bool
Default Value:: False
Flags:: READABLE, WRITABLE, EXPLICIT_NOTIFY

True if debug output should be exposed (for example by forwarding it to the journal), False otherwise.

New in version 2.72.