On Wed, 16 Jan 2019 at 15:52, Liam Proven
On 16/01/2019 14:51, Rainer Hantsch wrote:
All I said is: MINT and other distros are able to solve this issue, and therefore it is time that LEAP also has this issue solved.
So stop just asking for something impossible. Do your homework. *Work out why*.
Isolate what works, what driver, what kernel, whatever. And isolate what does *not* work in Leap.
Then you can make a specific request, and you will find that you get a more productive, positive response than you are getting here and now.
Indeed. In furtherance of that point, I am currently helping a colleague investigating an issue with their very new laptop that is struggling to boot with Leap/SLE in certain conditions. We have figured out that this failure to boot is _nothing to do_ with the kernel, mesa, Xorg, or almost all of the usual suspects that people request updates for in the name of hardware enablement. Therefore, we're currently having to experiment with changing _everything_ (ie. using Tumbleweed) and working back from there before filing the appropriate bug that we can at least scope to realise where the problem is. And when we get there, the appropriate maintainer(s) will find themselves having an appropriate bug report(s). And things will almost certainly be fixed. Such is life.. all software sucks in some way, things need to move forward to get better, openSUSE has the luxury of having multiple approaches to solving that conundrum. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org