Description of problem: The latest build (4/22/08) terminating PXE install after "Starting VNC..." Version-Release number of selected component (if applicable): anaconda 11.4.0.73 How reproducible: persisten Steps to Reproduce: 1. Prepare PXE install using following kickstart config. sample (f4d1) vnc --password install url --url http://192.168.3.102/a/fed/tst/Fedora/x86_64/os network --device eth1 --bootproto dhcp --hostname mazatlan1 lang en_US keyboard us rootpw install timezone America/New_York Sample command line use: label f64d kernel /fed/dev/x86_64/os/isolinux/vmlinuz append initrd=/fed/dev/x86_64/os/isolinux/initrd.img ksdevice=eth0 ks=http://192.168.3.102/a/ks/f4d1 2. 3. Actual results: Imediately after "Starting VNC..." it output the following error install exited abnormally [1/11] sending termination signals...done Expected results: should proceed without problem. Additional info: Using 2 network interface cards (NIC) having separate live network, DHCPs.
Does it fail if you don't specify the password?
Yes same problem without a password. It didn't matter whether to place "vnc" on the command line or kickstart file. I also tried it without relying on kickstart file and simply invoke "vnc" on command line only. Same problem.
Will -- haven't you done some vnc installs?
Huh! Yes, a couple of weeks ago I did. But I tried one with today's rawhide and sure enough: install exited abnormally [1/1] syslog sez: Xvnc[1422]: segfault at 33333333 ip 080a6ab1 sp bf9ca9f0 error 4 in Xvnc[8048000+3d6000]
f9-PR install host running vncviewer --listen port 5500 open boot off DVD, CD1 or boot.iso at menu press esc at the prompt linux vnc vncconnect=ip get the following errors: http://noname.math.vt.edu/Fedoraunity/vncss1.png http://noname.math.vt.edu/Fedoraunity/vncss2.png
Xvnc is segfaulting when run from anaconda -- our command line is Xvnc :1 -nevershared -depth 16 -geometry 800x600 -br leTimeout=0 -auth /dev/null -once DisconnectClients=false desktop=foo SecurityTypes=None although the simpler 'Xvnc :1' also sigsegvs. And although I don't _entirely_ trust gdb here... (gdb) bt #0 __glXScreenInit (pGlxScreen=0xa20fed0, pScreen=0xa20b090) at glxscreens.c:305 #1 0x080a6159 in __glXMesaScreenProbe (pScreen=0xa20b090) at glxglcore.c:426 #2 0x080a58b2 in GlxExtensionInit () at glxext.c:305 #3 0x0832de5d in main (argc=15, argv=0xbfbf6044, envp=0xbfbf6084) at main.c:367
Problem was in mesa package, vnc has to be rebuild against new one. Fixed in vnc-server-4.1.2-30.fc9
*** Bug 444430 has been marked as a duplicate of this bug. ***