line 423: [ply-boot-server.c:388] print_connection_process_identity:connection is from pid 677 (/bin/plymouth deactivate) with parent pid 668 (/usr/sbin/gdm3)
line 498: [./plugin.c:649] activate:taking master and scanning out
good:
line 402: [./plugin.c:649] activate:taking master and scanning out
line 573: [ply-boot-server.c:388] print_connection_process_identity:connection is from pid 711 (/bin/plymouth deactivate) with parent pid 665 (/usr/sbin/gdm3)
line 583: [./plugin.c:679] deactivate:dropping master
In the bad case, we don't see "dropping master" because boot_splash is NULL, because we were already deactivated.
I think it's like this (line numbers added)
bad:
line 423: [ply-boot- server. c:388] print_connectio n_process_ identity: connection is from pid 677 (/bin/plymouth deactivate) with parent pid 668 (/usr/sbin/gdm3)
line 498: [./plugin.c:649] activate:taking master and scanning out
good:
line 402: [./plugin.c:649] activate:taking master and scanning out server. c:388] print_connectio n_process_ identity: connection is from pid 711 (/bin/plymouth deactivate) with parent pid 665 (/usr/sbin/gdm3)
line 573: [ply-boot-
line 583: [./plugin.c:679] deactivate:dropping master
In the bad case, we don't see "dropping master" because boot_splash is NULL, because we were already deactivated.
I asked upstream about the attached patch, will see what they say and in the meantime it's on https:/ /launchpad. net/~laney/ +archive/ ubuntu/ plymouth if somebody would care to test.