diff options
| author | Jonas Ådahl <jadahl@gmail.com> | 2022-05-27 16:51:42 +0200 |
|---|---|---|
| committer | Marge Bot <marge-bot@gnome.org> | 2022-06-02 17:19:42 +0000 |
| commit | f5887a6258453bbba658e5b7e201df1fde3ae841 (patch) | |
| tree | 74b487161a02560a25f58b4d018d36dda34ede59 /src | |
| parent | 7bf4f850b8176fe3ace2ab09590d1de55c94318b (diff) | |
| download | mutter-f5887a6258453bbba658e5b7e201df1fde3ae841.tar.gz | |
monitor-manager: Make warning message less confusing
It talked about KMS state, which was a bit unexpected when debugging the
X11 backend.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2434>
Diffstat (limited to 'src')
| -rw-r--r-- | src/backends/meta-monitor-manager.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backends/meta-monitor-manager.c b/src/backends/meta-monitor-manager.c index 23f642f4f..6d9b7f416 100644 --- a/src/backends/meta-monitor-manager.c +++ b/src/backends/meta-monitor-manager.c @@ -3509,7 +3509,7 @@ meta_monitor_manager_real_read_current_state (MetaMonitorManager *manager) if (!meta_gpu_read_current (gpu, &error)) { - g_warning ("Failed to read current KMS state: %s", error->message); + g_warning ("Failed to read current monitor state: %s", error->message); g_clear_error (&error); } } |