http://bugzilla.opensuse.org/show_bug.cgi?id=1089116 http://bugzilla.opensuse.org/show_bug.cgi?id=1089116#c23 Bit Juggler <suse.junky@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WORKSFORME --- Comment #23 from Bit Juggler <suse.junky@t-online.de> --- (In reply to Stefan Dirsch from comment #22)
Honestly I meanwhile doubt, that Bumblebee works for anyone on Leap 15/TW.Why is this considered P0/Critical? It's even a manual process to configure it at all.
Well, when i look here (https://news.opensuse.org/) i can read "Based on enterprise code tested millions of times opensuse leap 15 released" and "openSUSE Leap 15 now allows migration to SLE, brings a new partitioner, integrates the Groupware Kopano, moves to Firewalld – and also comes distributed by Linode (for Cloud and infrastructure setups) and on high-end hardware like Tuxedo Laptops (other Cloud and hardware vendors will follow)." When i happen to have such a piece of "high-end hardware like Tuxedo Laptops" and i experience that an average user will not be able to install/use openSUSE Leap 15.0 on on it, then i think this is "Critical" and should be resolved as soon as possible. But may be i'm too much of a sales person. However i found a way out: After installing "xf86-video-intel" from the OSS repository the system starts up in graphic mode. Playing with the KDE compositor options i found that switching the rendering backend from "OpenGL 2.0" to "XRender" will remove the sluggish behavior of the the GUI. In openSUSE Leap 42.3 there was no need to install "xf86-video-intel" or to switch the KDE compositor backend to "XRender". Nor does any of the openSUSE docs (Release notes, SDB:Articles, ...) mention any of this. So i don't know whether i just found a workaround for a bug or whether that's the way it is intended to be. However for me it works so i consider this problem as solved. Thanks to everybody who helped me to solve this. -- You are receiving this mail because: You are on the CC list for the bug.