| Summary: | KWin 4.6 crashes after disabling direct rendering | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Thoar <thoar.varenkamp> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | phofin |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Thoar
2011-03-11 04:41:56 UTC
driver bug, sorry. FYI: DISabling direct rendering does NOT make things faster, rather the opposite. What you likely wanted to do is "suspend" compositing (SHIFT+Alt+F12) I guess the driver crashes because of the indirect rendering, re-enable it to get back a somehow stable system. KWin might mourn that you can't because your GL driver is cr... "broken". You can rearm this protection by passing kwriteconfig -file kwinrc -group Compositing -key CheckIsSafe true kwriteconfig -file kwinrc -group Compositing -key OpenGLIsUnsafe false in konsole (_before_ starting systemsettigns) *** Bug 274317 has been marked as a duplicate of this bug. *** |