Trying to reproduce the problem, I freshly installed below which is a good deployment.
ostree://fedora:fedora/rawhide/x86_64/silverblue
Version: Rawhide.20210511.n.2 (2021-05-11T23:30:14Z)
Commit: 46bc42198d7ba01dca6b126b6e210bbf31b2aad3ef5d31754ccac5e6194c9e9c
GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
Once I update to the latest by rpm-ostree update, I got a bad deployment.
ostree://fedora:fedora/rawhide/x86_64/silverblue
Version: Rawhide.20210514.n.0 (2021-05-14T06:04:28Z)
BaseCommit: 49fa46896e4ac009dc476f4149eb1ce526acd6fe40a54020391ccfe4de8d8b4f
GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
LayeredPackages: libguestfs-tools libvirt-client libvirt-daemon-config-network libvirt-daemon-kvm qemu-kvm virt-install virt-manager virt-top virt-viewer
(The problem still there without all the layered packages.)
Question:
Can I do a “bisect” of Deployments between 20210511 and 20210514 to determine which update caused this problem?
After reading the script, I am not sure how to make use of it:
The script is expecting a testscript which will determine if a deployment is GOOD or BAD. I have almost no skill on script writing. Thus not sure how to write a test script to determine if GDM hangs on start or not.
What is the correct way and where to mark the known GOOD entry and BAD entry?
Is it if my rpm-ostree status only have tww entries, which 0 is BAD and 1 is GOOD, then I can skip this step?