Bug 423911 - "OpenGL compositing has crashed KWin in the past"
Summary: "OpenGL compositing has crashed KWin in the past"
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (other bugs)
Version First Reported In: 5.18.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-05 20:21 UTC by darkpenguin
Modified: 2023-09-06 10:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description darkpenguin 2020-07-05 20:21:26 UTC
Pretty often (every few days), I notice tearing again, and that always means that I have to go to system settings and "Re-enable OpenGL detection".

I had this problem on Ubuntu Bionic LTS, upgraded to Focal LTS hoping it would be fixed there, but it is still a problem.

I have this on two systems, one with RadeonHD 5450 (radeon driver) and another one with Radeon RX550 (AMDGPU+radeon).

The problem is, I don't even know how to catch this problem when it happens. There is no error, I can only see that "it happened again IN THE PAST". It might be happening more often after a reboot, or maybe after something else.

How do I catch this bug? Are there any logs to watch, or could I maybe ask it to give me an error immediately when this happens?

Actually, I would be happy enough if I could disable OpenGL "detection" and simply force the settings I know are correct. If it crashes, it should just restart automatically. (I mean, the current behavior is good, but additionally it would be nice to have a way to disable it.)



SOFTWARE/OS VERSIONS:
Kubuntu 20.04 amd64
Kernel: 5.4.0-40-generic (HD5450) / 5.7.0-6.4-liquorix-amd64 (RX550)

KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Comment 1 David Edmundson 2023-09-06 10:38:24 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.