FS#50500 - [nvidia] KWin Compositing broken with 370.23

Attached to Project: Arch Linux
Opened by f (bakgwailo) - Tuesday, 23 August 2016, 19:14 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 08 October 2016, 14:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Upgrading broke KWin compositing for me. Downgrading restores it. Also happened with the AUR full-beta packages. This happens only on my laptop (Lenovo P50, Quadro M1000M, hybrid graphics disable in Bios/only Nvidia card is active). On my desktop (GTX970) the latest release is OK. Manually enabling/disabling compositing has no effect (although the screen to flicker/refresh when trying to enable it manually, it just seems to automatically disable it instantly).

Additional info:
* nvidia 370.23, kwin 5.7.3-1. Testing repos are enabled, system fully up to date.

Steps to reproduce:

Install/update to Nvidia 370.23 (official packages or full-beta from AUR). Restart computer. KDE/Plasma boots, log in, notice the screen flickers a bit like it wants to enable compositing, but it doesn't, and you are left with an uncomposited desktop. No errors/crash from KWin, and its not apparent in the system settings that it is disabled.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 08 October 2016, 14:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  kwin 5.7.5-1
Comment by f (bakgwailo) - Tuesday, 23 August 2016, 19:21 GMT
Please note that this affects the OpenGL 3.1/2.0 renders. Using the XRender back end re-enables effects. Let me know if there are any logs/etc I can provide.
Comment by Dmitri Kourennyi (DmitriK) - Wednesday, 24 August 2016, 15:32 GMT
I have the same issue with a Quadro K4100M. I've reported the bug to KDE (https://bugs.kde.org/show_bug.cgi?id=367766), though my gut tells me it's an Nvidia issue.
Comment by Dimos Dimoulis (dimosd) - Thursday, 01 September 2016, 05:54 GMT
I am sticking with nvidia 367 (long lived branch) with no problems. Nvidia 370 is beta, I think...
For me, short lived branch (and beta) nvidia drivers have been the major cause of instability on my system.
Comment by f (bakgwailo) - Thursday, 01 September 2016, 19:56 GMT
Unfortunately, it is a beta, but, all arch packages (including -lts) apparently were updated to 370.23.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 08 September 2016, 18:13 GMT
Please try 370.28.
Comment by Dmitri Kourennyi (DmitriK) - Thursday, 08 September 2016, 18:46 GMT
Just tried 370.28 from testing, but it didn't solve the issue for my setup.
Comment by f (bakgwailo) - Thursday, 08 September 2016, 21:10 GMT
Also just updated - still broken for me, too.
Comment by f (bakgwailo) - Saturday, 10 September 2016, 03:53 GMT
Also just updated - still broken for me, too.
Comment by f (bakgwailo) - Friday, 16 September 2016, 06:31 GMT
Upstream "fixed" it in the 5.7.5 release of Plasma - please close out.

Loading...