The nomodeset option is very commonly used as a debugging technique. Many experienced customers/partners try it (or *we* ask at first) when something doesn't work regarding the graphics. That said, you can't treat it for justification not to fix this bug :) I reported here just because this is a regression from Leap 42.2/42.3, thus you have a better chance to catch it. A good thing is that it appears just by replacing plymouth on the formerly working system. So you can bisect the failure, too, if any. There are lots of other bugs by plymouth (e.g. bug 966255 or bug 1020283). This bug itself might be irrelevant from others, but it's easier to reproduce, at least, thus here reported individually.