From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
It is possible to configure a display manger to launch Xvnc instead the regular
Xserver. This works with xdm for example, but not with gdm.
Looking into it I found an old hack that was applied to Xvnc to work around a
LinuxThreads bug that is no longer needed. Removing this hack makes Xvnc and gdm
Here is the patch.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Configure GDM to launch Xvnc
2.Notice that it doesn't work
3.Apply patch, recompile Xvnc, it now works.
Actual Results: n/a
Expected Results: n/a
diff -ur vnc_unixsrc/Xvnc/programs/Xserver/os/connection.c
--- vnc_unixsrc/Xvnc/programs/Xserver/os/connection.c Mon May 11 11:02:17 1998
+++ vnc_unixsrc-gurulabs/Xvnc/programs/Xserver/os/connection.c Tue Oct 15
@@ -379,7 +379,7 @@
BEGIN ORL VNC modification
Don't use SIGUSR1 - linuxthread uses this internally */
+/* no longer true 10/15/02 */
if (OsSignal (SIGUSR1, SIG_IGN) == SIG_IGN)
RunFromSmartParent = TRUE;
ParentProcess = getppid ();
@@ -388,7 +388,6 @@
kill (ParentProcess, SIGUSR1);
/* END ORL VNC modification
Created attachment 82805 [details]
Patch Xvnc to remove old work-around no longer needed that causes problems with GDM
Fixed in 3.3.3r2-41, which will appear in rawhide shortly. Thanks.