| Summary: | kwin crash after kernel update | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Paul Grabbe <pg7724> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 4.10.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Paul Grabbe
2013-03-21 16:59:59 UTC
bus error in memset. either the memory is corrupted or this is a driver bug FTR, cashes in glXBindTexImageEXT(display(), m_glxpixmap, GLX_FRONT_LEFT_EXT, NULL); what should cause a GL error or misbehaviour, but no crash. can you start the compositor during the session? (press shift+alt+f12) (In reply to comment #1) Although the automatic bug reporter started and caught this error upon login, the screen appeared as normal as if no error had occurred in kwin. After reporting the bug I logged out and then back in to see if the error would occur again, and it did not. After logging back in I did press shift+alt+f12 to toggle the compositor. Not having done this before I don't know what I should expect to see as a result. Pressed that combo a few times and did not see any visible effect. How can I check to see if the toggling took effect? Any other tests I should perform or does this look like a transient error? > bus error in memset. > either the memory is corrupted or this is a driver bug > > FTR, cashes in glXBindTexImageEXT(display(), m_glxpixmap, > GLX_FRONT_LEFT_EXT, NULL); what should cause a GL error or misbehaviour, but > no crash. > > can you start the compositor during the session? (press shift+alt+f12) (In reply to comment #2) > After reporting the bug I logged out and then back in to see if the error > would occur again, and it did not. Please watch out whether it re-occurs after the next cold boot. Could be an init bug in the driver or kernel module or whatever. > How can I check to see if the toggling took effect? "Present windows" (aka exposé) works - works not - works - works not. Windows would fade in smoothly with compositing and stuff like that. Setting worksforme unless reproducible. (In reply to comment #3) Did not reoccur after cold boot. I'm fine with setting status to WORKSFORME > (In reply to comment #2) > > After reporting the bug I logged out and then back in to see if the error > > would occur again, and it did not. > Please watch out whether it re-occurs after the next cold boot. > Could be an init bug in the driver or kernel module or whatever. > > > How can I check to see if the toggling took effect? > "Present windows" (aka exposé) works - works not - works - works not. > Windows would fade in smoothly with compositing and stuff like that. > > Setting worksforme unless reproducible. *** This bug has been marked as a duplicate of bug 315089 *** |