| Summary: | Kwin crashes with opengl | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | fri.K <fri.k> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version: | 4.11.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
fri.K
2013-12-21 14:20:00 UTC
driver bug. could be bug #328718 or bug #327310 (actually more like #327310) Just to be very sure about this: it happens with GL2 *and* GL3, but *not* with GL1? (In reply to comment #1) > it happens with GL2 *and* GL3, but *not* with GL1? In former release- yes, but I just have checked again and it's working with GL1.0. Then I switched to GL2.0 and it's also working. Now it only crashes if i try GL3.1 (always). After such attempt I must log off to try again GL2.0. It looks hardware/driver related because in other devices it works like a charm. long story short: driver and gpu combo do not support gl3 and the "modern" context creation is apparently broken to on failure cause an invalid state, leading to later segfaults in the driver. -> do not try to use GL3 *** This bug has been marked as a duplicate of bug 327310 *** (In reply to comment #3) > long story short: (..) > -> do not try to use GL3 Thanks, I think it's not a problem, but in future there could be some checker before showing this option or something. But as I said, it's not a problem for me. > Thanks, I think it's not a problem, but in future there could be some
> checker before showing this option or something. But as I said, it's not a
> problem for me.
well the problem is, that the test crashes :-)
(In reply to comment #5) > well the problem is, that the test crashes :-) You mean some UT or me as SCT? :) (In reply to comment #6) > (In reply to comment #5) > > well the problem is, that the test crashes :-) > You mean some UT or me as SCT? :) We cannot check the GL capabilities in the config dialog since drivers or (worse) broken driver installations may crash on that test, making the config dialog inaccessible - we had that :-( What *could* happen regarding bug #327310 would be to skip trying to create a GL3 context in kwin since we know it's not supported (what usually the failed creation would indicate) and this way we would bypass the driver bug (unless the driver start announcing GLCore support and crashing nevertheless ;-) (In reply to comment #7) > We cannot check the GL capabilities in the config dialog since drivers or > (worse) broken driver installations may crash on that test OK, I get it now. > What *could* happen regarding bug #327310 would be to skip trying to create > a GL3 context in kwin since we know it's not supported (what usually the > failed creation would indicate) In simple world probably it could be enough. But we are ugly creatures and one day I can start this OS in some hardware and another day in other. Only way I see it, is to force driver developers to fix it, at least function "isAvailable()" or whatever it calls. In my opinion KDE could only show message "Some hardware is broken, if it fails, try GL2 then. More info here". |