instead of letters i got only small rectangles. Seems like this is only on amd64. Found another person in forum with the same problem. Reproducible: Always Steps to Reproduce: 1. start vmware locally 2. 3. Actual Results: no lettes, only rectangles Expected Results: shuold have shown the right font If you need more information, let me know
Please try running vmware with the VMWARE_USE_SHIPPED_GTK=force environment variable set and verify whether the fonts are fixed. This sounds as though vmware is not able to correct initialize your local pango library, while the environment variable will force the use of the provided libraries...
Created attachment 127336 [details] output with export VMWARE_USE_SHIPPED_GTK=force
Sorry for the delay, I tried this : export VMWARE_USE_SHIPPED_GTK=force vmware The output is too long, so I put it in the attachment output.txt
another try : If I do the same but as normal user instead of root I got the same output but then it works. Seems like you're right looks like a problem with the pango library. Maybe this is on amd64 only?
Isn't there someone outsite who can fix this? I upgraded to vmware-server 1.0.4 these days but the problem is still the same. I also tried to do like this http://forums.gentoo.org/viewtopic-t-543623-start-25-postdays-0-postorder-asc-highlight-.html but this also fails in the first step.
As far as my understanding goes, when you run a gnome environment a gconf settings daemon is started for that user and all their appearance settings, etc, get taken from there. That includes theme and font/pango information. When you then swap to root and try to run another gtk program, root will attempt to start a gconf settings daemon also. I not sure why, but on some systems these seem to conflict, and the root daemon won't start. The program then won't get the correct theme or font information, which could result in the square boxes for letters. Sadly, I'm not sure what to suggest. 5:( If you find a solution, please post back here and let us know...
This also does not work if you run vmware as a normal user so I think that this is not a root daemon conflict
Can you please check whether this has been fixed since we're now up to version 1.0.8? If not, please reopen this bug, but if so then feel free to leave it as is. Thanks...
