Bug 15780 - "EXANoComposite" "1" crashes X in gtk2 apps
Summary: "EXANoComposite" "1" crashes X in gtk2 apps
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Acceleration/EXA (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-30 15:40 UTC by Andrew Randrianasulu
Modified: 2008-05-01 06:13 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
xorg.conf (6.42 KB, text/plain)
2008-04-30 15:41 UTC, Andrew Randrianasulu 		no flags Details
log (with NoTrapSignals enabled) (54.18 KB, text/plain)
2008-04-30 15:42 UTC, Andrew Randrianasulu 		no flags Details
gdb output (252 bytes, text/plain)
2008-04-30 15:43 UTC, Andrew Randrianasulu 		no flags Details
xorg.0.log without NoTrapSignals (55.70 KB, text/plain)
2008-04-30 15:44 UTC, Andrew Randrianasulu 		no flags Details
View All

Description Andrew Randrianasulu 2008-04-30 15:40:47 UTC 
Hello.

I'm using x server git (ce36ae526d88d20ff67cd6cb429fb06f48d231f6) + nouveau git (85536023ed7050632d121299ab99382e096b9984). I have one gtk2 app in autostart - gkrellm. It crash my sever with non-render capable (under nouveau) TNT2-class card. I can reproduce this crash with option "EXANoComposite" "1" too, on nv11. Bare X + gqview = same crash. Details will follow.
Comment 1 Andrew Randrianasulu 2008-04-30 15:41:45 UTC 
Created attachment 16277 [details]
xorg.conf
Comment 2 Andrew Randrianasulu 2008-04-30 15:42:52 UTC 
Created attachment 16278 [details]
log (with NoTrapSignals enabled)
Comment 3 Andrew Randrianasulu 2008-04-30 15:43:13 UTC 
Created attachment 16279 [details]
gdb output
Comment 4 Andrew Randrianasulu 2008-04-30 15:44:06 UTC 
Created attachment 16280 [details]
xorg.0.log without NoTrapSignals
Comment 5 Michel Dänzer 2008-05-01 06:13:03 UTC 
Fixed, thanks for the report.

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.