12-06-2021, 04:35 PM
(This post was last modified: 12-10-2021, 12:12 PM by Midas.
Edit Reason: Normalize "[SOLVED]" tag.
)
Hi,
Testing of the current release (1.0.62) with Solus Budgie 4.3 resulted in a blank screen and an eventual timeout script being initialised ending in a text prompt.
Pressing the enter key several times and waiting for a change was unsuccessful.
Same result observed for both MBR and GPT.
Surprised, as I'd read that Solus 4.2 had been tested successfully with Ventoy, I tried that release but it failed in the same way.
After discussion on the Solus forum revealed that the successful testing had been done using 1.0.41, I installed that and it worked first time!
I then updated to 1.0.62 which again led to the failure described above.
TLDR: It appears there is some regression from 1.0.41 to 1.0.62 regarding Solus but I've not tested other versions to identify when this occurred.
Not sure if it's a known issue but couldn't find any other bug report.
Please fix.
Testing of the current release (1.0.62) with Solus Budgie 4.3 resulted in a blank screen and an eventual timeout script being initialised ending in a text prompt.
Pressing the enter key several times and waiting for a change was unsuccessful.
Same result observed for both MBR and GPT.
Surprised, as I'd read that Solus 4.2 had been tested successfully with Ventoy, I tried that release but it failed in the same way.
After discussion on the Solus forum revealed that the successful testing had been done using 1.0.41, I installed that and it worked first time!
I then updated to 1.0.62 which again led to the failure described above.
TLDR: It appears there is some regression from 1.0.41 to 1.0.62 regarding Solus but I've not tested other versions to identify when this occurred.
Not sure if it's a known issue but couldn't find any other bug report.
Please fix.