Bug 530804
| Summary: | opening System Tools crashes X in F12Beta with intel | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard Schwarting <aquarichy> | ||||||
| Component: | pixman | Assignee: | Adam Jackson <ajax> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | rawhide | CC: | ajax, mcepl, xgl-maint | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | card_915GM | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-11-09 08:29:22 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Richard Schwarting
2009-10-25 10:58:02 UTC
I'll note that on another laptop, that opening System Tools (which I now realise is what About this Computer opens) does not crash X, but this other computer uses an AMD/ATI chipset. I'll note that it doesn't do it with Xephyr inside the same session. Created attachment 366076 [details]
Magic stacktrace
Here is a stacktrace that I obtained by doing this via SSH:
X :2
gdb --pid=<the PID of the above X session>
DISPLAY=:2 gnome-system-monitor
I couldn't do it locally because running gdb on X locally locks up my system (for some reason I don't understand).
If I could produce a more useful one with fewer values optimised out, I'll gladly do it.
I take it that the two uxa_ functions are the ones earlier reported in intel_drv.so in the less-useful stacktrace? I'll try with exa or xaa later, I guess. Using the "vesa" driver, I do not run into the same problem. System Monitor appears as expected, no crash. I tried to set Option "AccelMethod" "exa" and Option "AccelMethod" "xaa" and Option "NoAccel" "True" but from what I could tell from the Xorg.0.log, UXA was used anyway. Created attachment 366094 [details]
Xorg.0.log including crash with intel driver
This is the Xorg.0.log.old that's left behind after X crashes. Intel and presumably UXA acceleration.
I'll note that trying xorg-x11-drv-intel-2.9.0-3.fc12 xorg-x11-drv-intel-2.8.0-16.20090909.fc12 from koji suffered the same issue. (The beta comes with xorg-x11-drv-intel-2.9.0-2.fc12) *** This bug has been marked as a duplicate of bug 530803 *** |