http://bugs.winehq.org/show_bug.cgi?id=11740
Summary: Many invisible strings in forwarded nx (nomachine.com) session Product: Wine Version: 0.9.55. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: fonts AssignedTo: wine-bugs@winehq.org ReportedBy: francesco.fumanti@gmx.net CC: francesco.fumanti@gmx.net
Created an attachment (id=10988) --> (http://bugs.winehq.org/attachment.cgi?id=10988) screenshot of nx session with unvisible strings
Setup: - os: ubuntu 7.10 on a pentium 4 running the free edition of the nx server 3.1.0-5 from nomachine.com - wine: 0.9.55~winehq0~ubuntu~7.10-1 - nx client 3.1.0-6 running on a g4 with macosx - the pc running ubuntu and the are connected to the same local network (However, the bug also occured with previous ubuntu/wine/nx versions.)
Hello,
I am running ubuntu 7.10 on a headless pentium 4 to which I connect remotely from a ppc-mac by using nx from nomachine. The two computers are on the same local network.
When I start a windows application under wine, most of its strings in the application's menus, buttons,... are invisible. Most strings are even invisible in the "wine configuration" dialog.
However, when I set ubuntu to autologin and I use a vnc client to connect to the vnc server in the autostarted gnome session, the strings are all visible. (In other words, the problem does not occur when using vnc.)
Regards
Francesco
http://bugs.winehq.org/show_bug.cgi?id=11740
Francesco Fumanti francesco.fumanti@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #1 from Francesco Fumanti francesco.fumanti@gmx.net 2008-02-26 10:17:51 --- Sorry for filing this bug; the solution is here in the faq: http://wiki.winehq.org/FAQ under the chapter: Running winecfg has No text or damaged text displayed
http://bugs.winehq.org/show_bug.cgi?id=11740
Detlef Riekenberg wine.dev@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine.dev@web.de Severity|blocker |normal Status|RESOLVED |CLOSED
--- Comment #2 from Detlef Riekenberg wine.dev@web.de 2008-02-26 10:20:46 --- Not a blocker. User found the Problem with his System (fontforge).
Closing
http://bugs.winehq.org/show_bug.cgi?id=11740
--- Comment #3 from Dmitry Timoshkov dmitry@codeweavers.com 2008-02-26 10:26:02 --- (In reply to comment #2)
Not a blocker. User found the Problem with his System (fontforge).
The mentioned FAQ that has helped doesn't mention fontforge. It would be helpful if Francesco clarified what was the problem.
http://bugs.winehq.org/show_bug.cgi?id=11740
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2008-02-26 10:28:22 --- To me it looks like his system (a 64-bit ones) misses a 32-bit libXrender, or a libXrender.so symlink.
http://bugs.winehq.org/show_bug.cgi?id=11740
--- Comment #5 from Francesco Fumanti francesco.fumanti@gmx.net 2008-02-26 10:57:20 --- I am running wine in ubuntu 7.10 for the i386 architecture on a pentium 4
Maybe that the faq is right and the problem is really related to macosx... Anyway, the solution indicated in the faq solved the problem for me.
To clarify what I meant, I attached a screenshot to my first bug message.
http://bugs.winehq.org/show_bug.cgi?id=11740
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|PC-x86-64 |PC
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2008-02-26 22:00:21 --- (In reply to comment #5)
I am running wine in ubuntu 7.10 for the i386 architecture on a pentium 4
Then I have no idea why you specified x86-64 as a hardware platform.
http://bugs.winehq.org/show_bug.cgi?id=11740
--- Comment #7 from Francesco Fumanti francesco.fumanti@gmx.net 2008-02-27 05:53:42 --- @Dmitry
Sorry for the mistake in the platform setting. In fact, I guessed that x86-64 stood for 32bit and 64 bit, which considering your comment is probably not the case.
(As I was unsure, I gave many details in the first message of this bug thread.)