Description of problem: vncviewer does not use the same font path as a console. vncviewer appears to set a font path, rather than using the font server. This can cause interesting inconsistencies between console-based testing involving fonts and VNC-based testing. To fix this, set the font path (via "xset fp= unix/:7100" in your VNC session) to use the font server. Version-Release number of selected component (if applicable): vnc-4.1.2-9.el5 How reproducible: Always Steps to Reproduce: 1. Connect to a machine via VNC. 2. Attempt to run the test case in bug #189849 Actual results: Fails because of "Could not create fontset for -*-*-*-R-Normal--14-130-75-75-*-*" Expected results: Should just work. Additional info: I am unsure if the font server would always be unix/:7100. It might be better to figure out a way to query what the machine would normally do, and use that.
Are you really sure that this bug exists in rhel5? vnc works perfectly on rhel5 for me. I run vncserver, with default configuration and I've see nothing related to this bug (no error like "Could not create fontset.. "). Update rhel version or give me access for affected machine or upload server's logfile. Regards, Adam
I was also not able to reproduce this bug with mention file on RHEL5 machine
tested with bug #189849 Comment #12's Attachment
(In reply to comment #3) I was confused because this bug has been opened against rhel5. Let me check potential problems on rhel4 (also moving this bug to rhel4) -A-
I tried reproduce bug on up2date rhel4 system and I wasn't successfull. I also tested with bug #189849 Comment #12's Attachment and all works fine (no "could not create font path" message). If you're still able to reproduce this one, please reopen. -A-