Xvfb crashes with Segmentation Fault

[Martin Vysny]

How to reproduce this:
I run Xvfb :99 -ac, then DISPLAY=:99 gnome-terminal. When I kill gnome-terminal (with CTRL+C), Xvfb dies as well, throwing Segmentation Fault.

System:
Ubuntu Intrepid (I failed to reproduce this bug on Hardy)

$ gdb --args Xvfb :99 -ac
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/Xvfb :99 -ac
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x7f4e4fa2a6f0 (LWP 9417)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed

Program received signal SIGSEGV, Segmentation fault.
---Type <return> to continue, or q <return> to quit---
[Switching to Thread 0x7f4e4fa2a6f0 (LWP 9417)]
0x0000000000507665 in FreeColormap ()
(gdb) info stack
#0 0x0000000000507665 in FreeColormap ()
#1 0x000000000052a1cb in FreeClientResources ()
#2 0x000000000052a2b4 in FreeAllResources ()
#3 0x0000000000526adb in main ()

[Bryce Harrington (bryce)]

[This is an automated message]

Hi vyzivus,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Noah Z (junkmail9999)]

Please reopen this bug.

I was able to reproduce with the following commands on an up to date Ubuntu 8.10 64-bit install -
Xvfb :21324 -fbdir /tmp/xvfb_test -ac &
env DISPLAY=:21324 gnash -t 13 /tmp/xvfb_test/movie1.swf &
env DISPLAY=:21324 gnash -t 13 /tmp/xvfb_test/movie2.swf &
pkill -f /tmp/xvfb_test/movie1.swf
pkill -f /tmp/xvfb_test/movie2.swf

Attached the lspci -vvnn output, xorg log to follow.

[Noah Z (junkmail9999)]

Xorg log

[Noah Z (junkmail9999)]

Workaround has been stable for a few hours.
Instead of starting the Xvfb as stated, I added the extension argument -
Xvfb :21324 -fbdir /tmp/xvfb_test -ac -extension GLX &

Hope this helps someone else.

[Orbital_sFear (orbital-sfear)]

Confirmed -extension GLX work around.

I use a VPS running ubuntu server 8.10. I have already installed xorg, not sure if this is required for the workaround to work.

I tried out connecting several times and found the work around to function perfectly.

Thanks!

[dukat (dukat)]

This bug is still happening in Jaunty 9.04.

However, the GLX workaround is still valid.