vanilla-os / vib-fsguard Goto Github PK

Issue Description

Testing has been done on VirtualBox with Linux and Windows hosts, KVM on a linux host, and hyper-v on a Windows host.

VirtualBox on Linux failed to install for unrelated reasons with incredibly unstable graphics drivers and the inability of the installer to read the drive.

All the other hypervisors, Vanilla installed "correctly" but failed integrity check. Upon further investigation, the FsGuard executable is replaced with what appears to be log data, which would explain the IC failure.

Steps to Reproduce

-- disregard first two steps, this appears to not be exclusive to VMs
~~- Load a hypervisor (IE: Virtualbox, Hyper-V)

• Create a new VM (I used an 80GB drive, 8GB of ram, and 4 CPU cores, all other settings were tested first as default but changing them had no visible effect.)~~

• Install VanillaOS with the fairly obvious procedure

• Reboot when prompted and load current state (A)

• Observe IC fail. Bypassing IC boots correctly and seems to work, but attempting a forced update to fix the FsGuard executable unequivocally breaks both partitions, preventing Xorg or Wayland from launching in a current or previous state.

On what version of Vanilla OS this happens?

Orchid, latest as of 2024/07/02

Additional Information

The aforementioned issue with VirtualBox on Linux may be related to an issue discussed on the discord relating to the i915 drivers as the i915 chipset is used by default by VirtualBox on Linux hosts.

We need to investigate why this error is caused in the current version of the vib-fsguard plugin.

The full error log can be found at: https://github.com/Vanilla-OS/custom-image/actions/runs/9576449836/job/26404344197

Related PR: Vanilla-OS/custom-image#18

Release References

1. https://github.com/Vanilla-OS/vib-fsguard/releases/tag/v1.5
2. https://github.com/Vanilla-OS/Vib/releases/tag/v0.7.1
3. https://github.com/Vanilla-OS/vib-gh-action/releases/tag/v0.7.1