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
Describe the bug
The LogControl1 API doesn't affect logs emitted by polkit when --no-debug option is removed.
To Reproduce
To reproduce it it should be enough to remove the --no-debug option and set the LogLevel to crit. polkit keeps emitting messages like
Error performing authentication: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected (g-dbus-error-quark 4)
Error cancelling authentication: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
g_dbus_method_invocation_get_message: assertion 'G_IS_DBUS_METHOD_INVOCATION (invocation)' failed
g_dbus_message_get_unix_fd_list: assertion 'G_IS_DBUS_MESSAGE (message)' failed
16:57:03.311: Error converting subject to JS object: Process 786 terminated
Error converting subject to JS object: Process 786 terminated
Error getting process for system bus name `:1.99': GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: The connection does not existError performing authentication: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable (g-dbus-error-quark 2)Error getting process for system bus name `:1.99': GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: The connection does not existError cancelling authentication: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatableError cancelling authentication: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatableError calling GetUnitByPIDFD: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to get PID from PIDFD: No such processg_error_free: assertion 'error != NULL' failedProcess 786 terminatedg_error_free: assertion 'error != NULL' failedg_error_free: assertion 'error != NULL' failedg_error_free: assertion 'error != NULL' failed
Expected behavior
polkit should emit only critical messages (and the TRANSPORT should probably be syslog since the LogTarget property says that it all goes to syslog.
FWIW I agree with #425 (comment) that ideally --no-debug shouldn't be necessary. polkit could emit info messages by default and the LogLevel property could be used to control all the logs (by analogy with what all the systemd services do for example).
Describe the bug
The LogControl1 API doesn't affect logs emitted by polkit when
--no-debug
option is removed.To Reproduce
To reproduce it it should be enough to remove the
--no-debug
option and set the LogLevel tocrit
.polkit
keeps emitting messages likeExpected behavior
polkit should emit only critical messages (and the
TRANSPORT
should probably besyslog
since the LogTarget property says that it all goes tosyslog
.It was also discussed in #506 (comment)
The text was updated successfully, but these errors were encountered: