Description of problem: Running 'Xnest -ac -noreset :5' under gnome/gdm segfaults. Here is the output from 'gdb Xnest': (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208854112 (LWP 4287)] 0x082bd00b in PictureDestroyWindow () (gdb) where #0 0x082bd00b in PictureDestroyWindow () #1 0x082cdee4 in SDamageNotifyEvent () #2 0x082cd4c5 in SDamageNotifyEvent () #3 0x082c8a36 in SDamageNotifyEvent () #4 0x080853fa in NotImplemented () #5 0x0012a214 in __libc_start_main () from /lib/libc.so.6 #6 0x0805d3a1 in ?? () (gdb) Version-Release number of selected component (if applicable): xorg-x11-server-Xnest-1.1.1-5.fc6 How reproducible: Every time Steps to Reproduce: 1. install Xnest 2. 'Xnest -ac -noreset :5' 3. Actual results: Expected results: Additional info:
This appears to be a side effect of switching on Composite by default; since Xnest lacks Render support, and Composite requires it, things blow up quite nicely. I have a partial fix based on what I proposed in upstream Xorg bugzilla, but it doesn't work quite right yet.
Still segfaults with xorg-x11-server-Xnest-1.1.1-6.fc6
Still segfaults with xorg-x11-server-Xnest-1.1.1-8.fc6
Should be fixed now in xorg-x11-server-Xnest 1.1.1-11.fc6 or later.