[FreeNX-kNX] Problem with legacy app xclearcase (XListFonts or font handling maybe)
Florian Schmidt
fschmidt at gmx.at
Fri Jun 12 18:39:08 UTC 2009
Hi,
the xclearcase bug is based on how /etc/X11/Xressources is sourced. NX
handles Xressources as a directory (maybe this is default by mosts Linux
distributions, in Ubuntu it is). But Centos / RedHatEnterprise uses a file
as Xressources which is needed for xclearcase. For this you have to patch
you nxnode (/usr/bin/nxnode)
--- freenx-0.7.4.orig/nxnode 2009-02-25 16:17:28.000000000 +0100
+++ freenx-0.7.4/nxnode 2008-10-22 13:29:54.236040000 +0200
@@ -331,6 +331,8 @@
echo "Xft.dpi: 96" | DISPLAY=:$display xrdb -merge
>>"$USER_FAKE_HOME/.nx/C-$sess_id/session" 2>&1
[ -d /etc/X11/Xresources ] && xrdb -display :$display -merge
/etc/X11/Xresources/* >>"$USER_FAKE_HOME/.nx/C-$sess_id/session" 2>&1
+ [ -f /etc/X11/Xresources ] && xrdb -display :$display -merge
/etc/X11/Xresources >>"$USER_FAKE_HOME/.nx/C-$sess_id/session" 2>&1
+
#
# Startup the application
#
Hopefully I have time to release my freenx packages for Centos / RHEL next
week where this is one of the bugs fixed.
Cheers,
Florian
2009/6/12 Camilo Mesias <camilo at mesias.co.uk>
> Hi
>
> I've consulted the knowledge base but not found a solution.
>
> I have a legacy app that runs fine over VNC yet doesn't when using FreeNX.
>
> The server is CentOs and the client is Windows.
>
> The error message when the app doesn't run is:
>
> Error: Unable to create a text drawing font set.
>
> I have used xtrace to see what requests go to and from the X-server
> when the app starts and there seems to be a problem when the client is
> requesting font information. Over VNC I see this:
>
> 000:<:046b: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:046b:96: Reply to ListFonts: names={
> s='-misc-fixed-medium-r-semicondensed--0-0-75-75-c-60-iso8859-1'};
> 000:<:046c: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:046c:96: Reply to ListFonts: names={
> s='-misc-fixed-medium-r-semicondensed--0-0-75-75-c-60-iso8859-1'};
> 000:<:046d: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:046d:96: Reply to ListFonts: names={
> s='-misc-fixed-medium-r-semicondensed--0-0-75-75-c-60-iso8859-1'};
> 000:<:046e: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:046e:96: Reply to ListFonts: names={
> s='-misc-fixed-medium-r-semicondensed--0-0-75-75-c-60-iso8859-1'};
> 000:<:046f: 68: Request(50): ListFontsWithInfo max-names=0x0064
> pattern='-misc-fixed-medium-r-semicondensed--0-0-75-75-c-60-iso8859-1'
> 000:>:046f:296: Reply to ListFontsWithInfo:
> min-bounds={left-side-bearing=0 right-side-bearing=0 character-width=6
> ascent=-1 descent=-10 attributes=0x0000};
> max-bounds={left-side-bearing=2 right-side-bearing=
> [further output snipped]
>
> There are lots of ListFonts requests that generally are replied with a
> found name, followed by some ListFontsWithInfo that are replied with
> details.
>
> On FreeNX I get this:
>
> 000:<:03ae: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:03ae:32: Reply to ListFonts: names=;
> 000:<:03af: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:03af:32: Reply to ListFonts: names=;
> 000:<:03b0: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:03b0:32: Reply to ListFonts: names=;
> 000:<:03b1: 44: Request(49): ListFonts max-names=0x0001
> pattern='-*-*-*-*-*-*-0-*-*-*-*-0-ISO8859-1'
> 000:>:03b1:32: Reply to ListFonts: names=;
> 000:<:03b2: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:03b2:32: Reply to ListFonts: names=;
> 000:<:03b3: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:03b3:32: Reply to ListFonts: names=;
> 000:<:03b4: 68: Request(49): ListFonts max-names=0x0001
> pattern='-Misc-Fixed-Medium-R-SemiCondensed--0-0-75-75-C-60-ISO8859-1'
> 000:>:03b4:32: Reply to ListFonts: names=;
> 000:<:03b5: 44: Request(49): ListFonts max-names=0x0001
> pattern='-*-*-*-*-*-*-0-*-*-*-*-0-ISO8859-1'
> 000:>:03b5:32: Reply to ListFonts: names=;
> [further output snipped]
>
> In other words, the client is asking for fonts and the response is
> always nothing. It doesn't get as far as asking for ListFontsWithInfo.
>
> Other legacy apps work since I installed the legacy fonts in Windows
> as described here:
>
> http://www.nomachine.com/download-client-windows.php
>
> but this app refuses to work. I notice that the requests made are for
> uppercased query strings (eg. Misc) whereas responses come as lower
> case (eg. misc).
>
> I'm not sure how to proceed to get the legacy app to work, but it's
> mainstream for my user base, so people will continue to use VNC while
> FreeNX can't work with the app :( Has anyone got any ideas to work
> around or fix the problem?
>
> Thanks in advance,
>
> -Cam
> ________________________________________________________________
> Were you helped on this list with your FreeNX problem?
> Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
>
> Don't forget to check the NX Knowledge Base:
> http://www.nomachine.com/kb/
>
> ________________________________________________________________
> FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090612/41026671/attachment.html>
More information about the FreeNX-kNX
mailing list