Red Hat Bugzilla – Bug 437899
Enabling composite with r300 crashes X server
Last modified: 2018-04-11 07:53:26 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Use the default composite extension, try to load X, it will crash with a stack
dump (will provide in a bit)
Steps to Reproduce:
1. Launch X as a normal user (startx) or use KDM (KDE 4.x)
2. X server will crash with segfault and produce a dump
Crashes when composite is attempted to be used
Application requesting composite launches normally.
Rawhide snapshot. I'll provide stackdump later today.
Note: I am use XAA no EXA for software acceleration
kdeinit4: Got EXEC_NEW '/usr/local/kde4/bin/kgpg' from launcher.
kdeinit4: preparing to launch /usr/local/kde4/bin/kgpg
0: X(xf86SigHandler+0x79) [0x80bc2d9]
2: X(miHandleValidateExposures+0x37) [0x8127827]
3: X(UnmapWindow+0x1f8) [0x80702c8]
4: X(compFreeClientWindow+0x2d3) [0x8143b43]
5: X [0x813f604]
6: X(FreeResource+0x10c) [0x806dacc]
7: X(compUnredirectWindow+0x8b) [0x8142f0b]
8: X [0x813fe5c]
9: X [0x8127e45]
10: X [0x8127e57]
11: X(miChangeSaveUnder+0x6b) [0x8127efb]
12: X(MapWindow+0x37b) [0x8070a2b]
13: X(ProcMapWindow+0x69) [0x8085119]
14: X(Dispatch+0x34f) [0x808599f]
15: X(main+0x47d) [0x806b31d]
16: /lib/libc.so.6(__libc_start_main+0xe6) [0x418606]
17: X(FontFileCompleteXLFD+0x22d) [0x806a701]
I should also note I am building KDE '4.1' from their svn trunk so I don't know
if this is triggering some new bug in Xcomposite.
Created attachment 298322 [details]
Created attachment 298324 [details]
Xorg crash with full debug
This is quite certainly not stacktrace from Xorg. Trying compiz, but not sure.
This comes from KDE 4.x (in this case KDE 4.1) not compiz, Kwin also supports
composite effects like compiz does.
This bug is also logged in https://bugs.freedesktop.org/show_bug.cgi?id=15100
The stacktrace is from Xorg (libXcomposite and core X server)
Note, disabling backing store in xorg.conf gets me no crashing.
Option "BackingStore" "false"
Lower priority, still a bug, but this is totally workaroundable.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Oh close this, we're in KMS now, and this bug is totally moot.