On Fri, 2023-04-28 at 08:40 -0400, Pablo Sanchez wrote:
Early on, on the physical installation, I had the very same grub issue on a full wipe-install. I re-did the installation, paying careful attention the next time, and everything worked.
All to say, it may not be a bug with the installer per se but perhaps the UI needs to be updated to help those who may not be paying full attention. Like me that time. :)
While I don't know if that's what happened with the video creator but given their Linux experience, it's possible given their experience with different distros he may have not read the prompts carefully.
The problem here is that it's all speculation. The only viable thing would have been to at least manage to collect yast logs - something we could go on later in a bug report. I'm not trying to dismiss the problem at all! The fact that it happened (even only a single time) is a very bad data point - and we should try to address it. All the 'clicking around in the partitioner' might have resulted in an invalid setup (sorry, it's an advanced installer, we expect you to know what you do) or, worse, yast got confused and did some wrong assumptions. In the first case, yast should probably be more clear in claiming: you go 'expert mode - I have to little capability to fully understand what you do there. you are on your own' In the 2nd case, yast should not have been confused of course. but, as said: no logs from the botched installation - no way we can even ask the yast team to try to fix it :( If anybody ever gets to such a point: try to boot with a rescue system and store away at least the yast logs (/var/log/YaST2) - they are quite verbose and the YaST Team does a fantastic job finding the needle in the heystack when it comes to those logs. Cheers Dominique