plymouth/0005-event-loop-Remove-ply_trace-calls-around-the-disconn.patch
Hans de Goede f97cb31771 Add patches fixing crash on monitor hot(un)plug (rhbz#1809681)
Add patches fixing delay between gdm telling us to deactivate and
  us telling gdm it is ok to continue
Drop plymouth-plugin-throbgress sub-package, the spinfinity theme now
  uses the two-step plugin
2020-03-09 10:58:24 +01:00

44 lines
1.8 KiB
Diff

From 9c25da99889439924eeae953f357233bdb99d569 Mon Sep 17 00:00:00 2001
From: Hans de Goede <hdegoede@redhat.com>
Date: Tue, 18 Feb 2020 21:19:38 +0100
Subject: [PATCH 5/7] event-loop: Remove ply_trace calls around the disconnect
handler
Doing a ply_trace both before and after the disconnect handler, which
gets called every time a boot client asks something of us through by
calling /sbin/plymouth leads to a lot of not really informative messages
in the debug-log.
This removes the 2 ply_trace calls around the disconnect handlers to make
the logs easier to read.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
src/libply/ply-event-loop.c | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/src/libply/ply-event-loop.c b/src/libply/ply-event-loop.c
index 5eb601c..57751c2 100644
--- a/src/libply/ply-event-loop.c
+++ b/src/libply/ply-event-loop.c
@@ -1061,15 +1061,9 @@ ply_event_loop_handle_disconnect_for_source (ply_event_loop_t *loop,
destination = (ply_event_destination_t *) ply_list_node_get_data (node);
next_node = ply_list_get_next_node (source->destinations, node);
- if (destination->disconnected_handler != NULL) {
- ply_trace ("calling disconnected_handler %p for fd %d",
- destination->disconnected_handler, source->fd);
+ if (destination->disconnected_handler != NULL)
destination->disconnected_handler (destination->user_data, source->fd);
- ply_trace ("done calling disconnected_handler %p for fd %d",
- destination->disconnected_handler, source->fd);
- }
-
node = next_node;
}
}
--
2.25.1