|Summary:||vnc does not work with F13 Alpha TC2|
|Product:||[Fedora] Fedora||Reporter:||Orion Poplawski <orion>|
|Component:||anaconda||Assignee:||Ales Kozumplik <akozumpl>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||13||CC:||jonathan, jzeleny, milan.kerslager, vanmeeuwen+fedora|
|Fixed In Version:||anaconda-13.35-1.fc13||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-03-17 16:26:25 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Orion Poplawski 2010-02-16 15:43:12 UTC
Description of problem: Doing pxe/ks install. ks.cfg has: install vnc VNC server is started, but all install messages go to text screen on VT1. Version-Release number of selected component (if applicable): 13.26
Comment 1 Ales Kozumplik 2010-02-17 10:30:43 UTC
Hi Orion, This is strange. I tried on TC2 from: http://serverbeach1.fedoraproject.org/pub/alt/stage/13-Alpha.TC2/Fedora/i386/ Using pxe plus the exact kickstart you provided VNC starts fine for me and I can connect to it from the Gnome's Remote Desktop Viewer 2.28.1. Did you notice the that the port has to be 1, so the address for the remote viewer looks like e.g. "10.34.39.30:1"? Otherwise if the port number isn't the problem, can you please attach logfiles and describe what you see in the terminal? Is it the blue textual interface or just some log messages? Thank you. Ales
Comment 2 Orion Poplawski 2010-02-17 17:03:58 UTC
Created attachment 394773 [details] anaconda.log Here's the anaconda log. I see the normal blue text interface on VT1, VNC display is running and I can connect, but it is black. I'm also using updates-565692.img to work around another anaconda bug so maybe that is causing trouble.
Comment 3 Ales Kozumplik 2010-02-22 12:54:00 UTC
Hi Orion, according to the log file, there is also a %pre section in your kickstart. Can you please the entire kickstart file? Thanks, Ales
Comment 4 Ales Kozumplik 2010-02-22 16:16:30 UTC
Taking the needinfo back, I think I've found the root cause.
Comment 5 Ales Kozumplik 2010-03-05 09:45:11 UTC
The fix for f13: 3781b3074893422638037fc90ed6e78345d1e2cc, should be released with anaconda-13.34.
Comment 6 Orion Poplawski 2010-03-17 16:26:25 UTC
Verified with 13.35 in Beta-TC0.
Comment 7 Ales Kozumplik 2010-03-18 08:01:39 UTC
*** Bug 572123 has been marked as a duplicate of this bug. ***
Comment 8 Fedora Update System 2010-03-18 17:22:33 UTC
anaconda-13.35-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.35-1.fc13
Comment 9 Fedora Update System 2010-03-23 02:26:03 UTC
anaconda-13.35-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.