| Summary: | sna: screen corruption with glx-dock (cairo-dock) | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Matthew Monaco <dgbaley27> |
| Component: | Drivers/DRI/i915 | Assignee: | Ian Romanick <idr> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | dgbaley27 |
| Version: | 8.0 | Keywords: | licence |
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Corrupt Screen
Normal Screen dmesg.log Xorg.log |
||
|
Description
Matthew Monaco
2012-09-04 20:35:20 UTC
Created attachment 66632 [details]
Corrupt Screen
Created attachment 66634 [details]
Normal Screen
Created attachment 66635 [details]
dmesg.log
Created attachment 66636 [details]
Xorg.log
To be the bearer of bad news, that is looks just like a mesa bug. Cat ~/.xsession-errors would be a good one to check. Sorry, I thought that since it only happened with SNA... I can reproduce the bug without any new output in .xsession-errors. However, if click the dock applet, and refresh the screen a few times, I eventually see: error 8: BadMatch (invalid parameter attributes) request 152 minor 6 serial 56132 error 9: BadDrawable (invalid Pixmap or Window parameter) request 149 minor 4 serial 56133 error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0 serial 56183 Using cairo-dock-3.0.2 on debian and cairo-dock -o, it renders incorrectly using UXA or SNA, so I'm not convinced that it is bug free to begin with... And since it can't keep track of its own Pixmaps.... If you think it is worth persuing, your best bet is to try recompiling xf86-video-intel with --enable-debug (and perhaps --enable-debug=full) to see if that catches anything obvious. I definitely /cannot/ reproduce the corruption with UXA. However, I still see those three lines after a bit of mucking with the dock in .xsession-errors. I don't exactly follow your meaning, do you now think it might be a cairo-dock bug rather than mesa? I'll recompile and post Xorg.log soon. It's definitely worth pursuing, I'm just not sure where =) The garbage you have on your screen looks like a mesa bug, as if it is keeping stale data around in its state tracker. The misrendering I see (where the wrong icons are drawn at the wrong time) is a cairo-dock bug. The errors reported for invalid pixmap is a cairo-dock bug. Don't know if this helps anymore, but I recompiled so I'm posting it: http://wikisend.com/download/962562/Xorg.debug.log.gz (nb: I've never used or heard of wikisend before, but it is ok with a 16M file) I'm switching the product to mesa, might someone from mesa take a look at the corruption to see if it might be a mesa problem? Hello Matthew, is this still valid with latest SW?? Thank you. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/716. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.