You made a general remark without direct connection to any post in this thread. Thus the reader, including me, could think you are refering to the last post from OrsoBruno.
Please note:
If my post would have refered to another post, it would be marked as an answer (like this post is to your’s )
Moreover I didn’t made a “general remark”, but asked for information on the issue of this thread, so me (and the forum) can benefit by learning.
No, you did not. You answered to the last post in this thread and asked why OrsoBruno recommended to use update-bootloader. Now later, after you saw that you created confusion, you say that you want to know the reason for the TO’s issue.
Likely the newer hardware… This sort of thing occurs often in the likes of Leap releases as it doesn’t track upstream developments.
For Leap it generally requires a bug report to get the appropriate changes back-ported by the maintainer(s) so the option can be removed, else it will be present forever…
I had a look at the former provided link at first place…
However… in the linked thread it links to at least 2 other threads,
and - as far as I understand - none of it states the origin cause.
Moreover:
As the threads are abt. 2y/o one should expect (?) the issue should
have been adressed in openSUSE meanwhile…(?). But obviously
in Leap 16.0 it still is not.
And last but not least this thread’s starter doesn’t said, what kind
of option actually solved his problem.
To summarize:
We know that adding some kind of options solves this thread’s problem.
We don’t know the cause (linked threads and now),
we don’t know if it’s been fixed (linked threads),
we don’t know if it’s been issued for Leap 16.0 and
we don’t know the exactly fix of this thread’s problem.
@user42 This is likely because no one reported it as a bug… Maintainers can’t fix things they don’t know about, or have hardware to duplicate, this is why bugs need to be reported…
Forum threads/solutions do not suffice in a lot of cases.
I’m very sorry to hear that.
That’s something I’m used to at M$ - but wouldn’t have expected it at Linux/ openSUSE too.
Moreover (as I already wrote at another place), naming explitely the cause and solution may not be expected by a “simple user”, even less reporting bugs, but maybe by the senior posters who know the where and how and are accounted already.
For the sake of openSUSE.
Malcolm, that topic at the side panel is a damned good idea!
Nevertheless I would like to encourage the senior posters who have the experience and knowledge of Linux/ openSUSE insides to report a bug: if the forum user probably won’t (be able to even express it, due to missing openSUSE/ Linux experience) do it.
(If I will ever be… I promise to do myself )
I can’t if I don’t have hardware or software to duplicate the issue when the bug report assignee asks questions, it really does have to be the person with the issue.
If a user is not sure, just ask for guidance in the forum, someone will help out…