http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c1 Stefan Knorr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Stefan Knorr --- Added a note with: https://github.com/openSUSE/release-notes-openSUSE/blob/1f8056b9b180898fba82... Please see if it's ok -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c3 --- Comment #3 from Stefan Knorr --- Thanks, Stefan. 1) Can you name what other issues there are? Maybe just in terms of a category like "stability issues", "rendering issues" ... It is important to let users know that this demotion of a fairly important happened for a reason. Hence my moving the KDE issues to the beginning of the text. 2) Okay, that is probably better. 3) I can change that to "...which mitigate the KDE issues, ...". But indeed it depends on (1). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c5 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alarrosa@suse.com, | |fvogt@suse.com --- Comment #5 from Ludwig Nussel --- (In reply to Stefan Dirsch from comment #0)

Please add this to Leap 42.2 release notes. Thanks!

-- Nouveau 3D/DRI driver disabled by default

With Leap 42.2 we are forced to consider the nouveau DRI/3D driver as experimental.

Why now and not in 42.1? Are there bug reports that back this?

Customers not interested in installing the proprietary NVIDIA driver for fast 2D/3D support can install this package, though at their own risk. Unfortunately the nouveau DRI driver does not work together with current multithreaded KDE apps.

What does that mean? Crash, lockup, display glitches? How bad? NVidia cards are pretty wide spread and KDE is the default desktop. We need a bit more than release notes documentation if we know that this combination is broken.

We have prepared patches for Mesa to mitigate this issue, but have not included them as per the author's intent: Using them may deadlock the system. Experienced users running KDE and willing to use these patches can rebuild the Mesa package after setting use_broken_nouveau_locking_patches %define in specfile to 1.

Remove that paragraph. Recompiling Mesa is out of scope for the target audience. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c7 --- Comment #7 from Stefan Dirsch --- (In reply to Ludwig Nussel from comment #5)

(In reply to Stefan Dirsch from comment #0)

...

Please add this to Leap 42.2 release notes. Thanks!

-- Nouveau 3D/DRI driver disabled by default

With Leap 42.2 we are forced to consider the nouveau DRI/3D driver as experimental.

Why now and not in 42.1? Are there bug reports that back this?

Sure. Multithreaded KDE apps no longer start with nouveau DRI driver. KDE on 42.1 did not use this feature yet.

...

Customers not interested in installing the proprietary NVIDIA driver for fast 2D/3D support can install this package, though at their own risk. Unfortunately the nouveau DRI driver does not work together with current multithreaded KDE apps.

What does that mean? Crash, lockup, display glitches? How bad? NVidia cards are pretty wide spread and KDE is the default desktop. We need a bit more than release notes documentation if we know that this combination is broken.

KDE apps are crashing immediately.

...

We have prepared patches for Mesa to mitigate this issue, but have not included them as per the author's intent: Using them may deadlock the system. Experienced users running KDE and willing to use these patches can rebuild the Mesa package after setting use_broken_nouveau_locking_patches %define in specfile to 1.

Remove that paragraph. Recompiling Mesa is out of scope for the target audience.

Fair enough. We tried to address the issue with these locking patches, which improved the situation a lot. Later we figured out that upstream does not want to have these patches applied, since they believe they can easily deadlock the userspace. So we had the idea to make everybody happy. Normal cutomer, nouveau upstream and experienced users. Oh well ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c8 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de --- Comment #8 from Fabian Vogt --- To clarify, this affects all KDE apps using the Qt WebEngine module, so mainly KMail, kontact and other PIM apps. Plasma itself and applications not using it are not affected. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c9 --- Comment #9 from Antonio Larrosa --- Just for the record: The issue reported at Qt's bug tracker: https://bugreports.qt.io/browse/QTBUG-41242 The issue reported at mesa's bug tracker: https://bugs.freedesktop.org/show_bug.cgi?id=91632 A branch of mesa trying to fix this issue: https://github.com/imirkin/mesa/commits/locking (not updated since July, but apparently stable according to a comment) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1003402 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c13 --- Comment #13 from Stefan Dirsch --- (In reply to Antonio Larrosa from comment #11)

I've just known of this issue this morning. I'm now working on patching qt-webengine so it doesn't use the gpu when nouveau is used, I think that might help. What do you think?

I wasn't aware that would be possible. This definitely should help, yes. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c15 Antonio Larrosa changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sndirsch@suse.com | |) --- Comment #15 from Antonio Larrosa --- Stefan (In reply to Stefan Dirsch from comment #13)

(In reply to Antonio Larrosa from comment #11)

...

I've just known of this issue this morning. I'm now working on patching qt-webengine so it doesn't use the gpu when nouveau is used, I think that might help. What do you think?

I wasn't aware that would be possible. This definitely should help, yes.

Hmm, I can't reproduce your problems on rana (nvidia G98 [Quadro NVS 295]). Can you create a user for me in a system that shows this problem and give me ssh access to it? You can read on https://bugzilla.suse.com/show_bug.cgi?id=1003402#c32 and https://bugzilla.suse.com/show_bug.cgi?id=1003402#c33 what I could reproduce (and fix), but I don't get any crashes like you did. What If you could join irc tomorrow, I would like to debug this on your test machine. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sndirsch@suse.com | |) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Bug 1005323 depends on bug 1003402, which changed state. Bug 1003402 Summary: Plasmashell dumps core with nouveau graphics http://bugzilla.suse.com/show_bug.cgi?id=1003402 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Max Staudt changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1003402 Blocks| |997171, 1003402 Depends on|1003402 | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c25 --- Comment #25 from Dominique Leuenberger --- Just a side note: the GNOME Team did some tests with nouveau-dri missing on a system with an nvidia chipset: this basically renders Leap 42.2 GNOME on an nvidia system totally unsatisfactory slow until the user either installs the Mesa-dri-nouveau or the binary blob driver (we can work around this by adding Mesa-dri-nouveau to the GNOME pattern, but still) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c27 --- Comment #27 from Fabian Vogt --- (In reply to Stefan Dirsch from comment #26)

The situation with nouveau in the past was:

If the driver works for you be happy and use it. If it doesn't, don't waste your time and install NVIDIA (we recommend to prefer Intel or AMD over NVIDIA GPUs since ages!).

This now changed with KDE to:

Either switch to another desktop or install NVIDIA.

It did not. Nouveau has _always_ been breaking Qt Webengine on _all_ cards. Just now some KDE applications in the PIM stack (that is not used by the majority even) and some other third-party applications (like Otter Browser) are affected. This is not a bug in chromium itself, but rather that Qt and Chromium do not share rendering threads. A workaround might be do disable the Qt hardware accelerated rendering (export QT_OPENGL=software). Antonio, can you test that? If that works, we can just put something like "(lsmod | grep nouveau) && export QT_OPENGL=software" into the startkde script, which wouldn't even have a big impact on performance. The other issue is that KDE does not even start on _some_ cards due to a bug in nouveau. All it takes to work around this is forcing XRender using an environment variable or just changing an option in ~/.config/kwinrc. So if you're using nouveau without KDE PIM, everything is still fine except on cards where nouveau is generally unstable. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c29 --- Comment #29 from Richard Brown --- (In reply to Ludwig Nussel from comment #21)

3) do something in yast a) switch default desktop to gnome if Nouveau b) change default desktop in general

Ludwig, the Board and I have discussed this and given the circumstances you have our full support and backing to investigate these options. We have to ensure that the default experience of users to Leap 42.2 is the best first impression we can give to new users, and while of course we want to offer the best KDE experience available, the lack of support for a commonly available graphics card and the only drivers we can easily distribute make it ineligible for the role of the default

c) warn if KDE is used on Nouveau systems d) warn about instablities with Nouveau in general

I'm working on wording for these two options, as I still think it's a good idea even if we decide to take a different default -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c32 Richard Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown@suse.com --- Comment #32 from Richard Brown --- (In reply to Felix Miata from comment #31)

Whatever solution is chosen looks like will provide vexations on systems used to test for behavioral differences that depend on the driver in use, aka swapping among various PCIe gfxcards like I do on host big41.

Does that machine actually do any real world work besides theoretical testing of nonsense workloads? Let's ensure openSUSE works on scenarios real humans run into before improving our coverage to theoretical use cases. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Luca Beltrame changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbeltrame@kde.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c38 --- Comment #38 from Stefan Dirsch --- (In reply to Max Staudt from comment #36)

Just to make sure we're on the same page: We'd strip nouveau's 3D support from Mesa, while leaving the kernel driver in place. That means that Xorg's modesetting DDX or nouveau's DDX can still set beautiful 2D resolutions via KMS, but just not activate 3D support as it is missing from Mesa.

Exactly. BTW, GLAMOR support has been removed from nouveau driver. So we won't lose 2D acceleration either as long as EXA is still supported by the GPU. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c42 --- Comment #42 from Ludwig Nussel --- could someone please submit packages with the mentioned supplements? The warning text is handled in a separate package. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c44 --- Comment #44 from Stefan Dirsch --- (In reply to Ludwig Nussel from comment #42)

could someone please submit packages with the mentioned supplements? The warning text is handled in a separate package.

done https://build.opensuse.org/request/show/437179 https://build.opensuse.org/request/show/437177 Feel free to remove the SR, which is not needed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c46 --- Comment #46 from Bernhard Wiedemann --- This is an autogenerated message for OBS integration: This bug (1005323) was mentioned in https://build.opensuse.org/request/show/437240 Factory / openSUSE-EULAs https://build.opensuse.org/request/show/437241 42.2 / openSUSE-EULAs -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c49 --- Comment #49 from Bernhard Wiedemann --- This is an autogenerated message for OBS integration: This bug (1005323) was mentioned in https://build.opensuse.org/request/show/437522 Factory / openSUSE-EULAs -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:3469:moderate |maint:planned:update |maint:planned:update | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 http://bugzilla.suse.com/show_bug.cgi?id=1005323#c56 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED Flags|needinfo?(lnussel@suse.com) | --- Comment #56 from Ludwig Nussel --- Ah, I already answeredt he pull request. The section is fine as it is. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|maint:planned:update |maint:planned:update | |obs:running:5832:moderate -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1005323 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:5832:moderate | -- You are receiving this mail because: You are on the CC list for the bug.