| Summary: | OpenGL 2 compositing setup failed | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Buck Shockley <darkwingbuck13> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | major | CC: | frederick888, leguen.yannick |
| Priority: | NOR | Flags: | mgraesslin:
NVIDIA+
|
| Version: | 5.10.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Buck Shockley
2017-07-19 03:53:41 UTC
NVIDIA? Yes, nvidia 375.66 I'm sorry, but this is a problem with the NVIDIA driver. Up to 5.10.3 KWin used to crash on NVIDIA in certain situations. In 5.10.3 we fixed this by implementing an NVIDIA specific extension for that crash. Due to that we were starting to see freezes which we fixed in 5.10.3.1 (emergency release). After that got fixed we got crashes in situations like this here - fixed in 5.10.4 and now we see compositing failing to start again. The idea is to prevent crashes of the compositor. If nvidia thinks that OpenGL should not work at all - so be it. Running Kwin 5.10.4 here, with nvidia drivers too (GTX 950). In my case, after running fullscreen games like Xonotic, kwin successfully enables compositing again. However, almost every time I start the Steam client, compositing is disabled and then it's impossible to enable it again, even with Alt+Shift+F12. Switching to the OpenGL 3.1 backend looks like a good workaround, though, as I don't have any issue with it. The problem mentioned above only happens with the OpenGL 2 backend. Literally has barely got a single day issueless since Nvidia switched to proprietary drivers. Sometimes fails Xorg, sometimes desktop, sometimes FFmpeg... I know crafting a driver is bloodily difficult but still shame on them. Ok, forget what I said in my previous comment... I just had the same issue with the OpenGL 3.1 backend (starting Steam will disable kwin compositing, and it won't enable it again). (In reply to Yannick from comment #6) > Ok, forget what I said in my previous comment... > > I just had the same issue with the OpenGL 3.1 backend (starting Steam will > disable kwin compositing, and it won't enable it again). Every time I've had this problem, it's been directly related to Steam. It happened just now when trying to launch TF2 after it crashed. Exact same error in journalctl. This may be a stupid question, but I noticed a couple other things sometimes popping up at the exact same time in journalctl: Jul 31 23:49:01 buck-pc kernel: NVRM: Xid (PCI:0000:01:00): 31, Ch 00000030, engmask 00000101, intr 10000000 Jul 31 23:49:01 buck-pc kwin_x11[1006]: Error loading text-to-speech plug-in "flite" Jul 31 23:49:01 buck-pc kwin_x11[1006]: kwin_core: OpenGL 2 compositing setup failed Jul 31 23:49:01 buck-pc kwin_x11[1006]: kwin_core: Failed to initialize compositing, compositing disabled The Arch wiki says the NVRM bit is related to hardware acceleration in Flash and a reddit post on /r/kde described an identical log output, even with the flite error. Could this be related to bug 381870? These messages are most likely unrelated. |