Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#29763 - [nx] fonts and color problem with old style X applications
Attached to Project:
Arch Linux
Opened by Alexey Talikov (ruata) - Saturday, 05 May 2012, 12:25 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 21 September 2012, 18:35 GMT
Opened by Alexey Talikov (ruata) - Saturday, 05 May 2012, 12:25 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 21 September 2012, 18:35 GMT
|
DetailsDescription:
Not optimal default fonts search path. Can't find rgb file (recent Xorg versions) Additional info: * nx 3.5.0.12-2 Steps to reproduce: Login remotely with NX client Run pure X application like xterm As I know it uses server side resources and if can't find rgb file you can't see any text Patches for nx are attached. Paths are little bit specific to my setup, but they are for reference |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Friday, 21 September 2012, 18:35 GMT
Reason for closing: Won't fix
Friday, 21 September 2012, 18:35 GMT
Reason for closing: Won't fix
fonts.diff
Anyone else thinks this should be done inside nx pkg?
- I don't have a directory on my NX server called /usr/lib/nx/share/rgb - and we can't assume the server is running ArchLinux at all.
- For what program is oscolor.c used for? Do we ship any file in our "nx" subpackages that is based on this file?
fonts:
- why is it needed to switch the DEFAULT path with Alternate 3 that we use in Arch? Shouldn't nxagent fallback to alternate3 in our case?
I can well login into my Arch running NX server and start xterm in my Xfce session. All letters are properly shown.
As I know old type X applications use client side resources, but get path from server.
NX uses quite old X components, that's why no problem to run locally with recent Xorg version
This file is located on the client.
pacman -Qo /usr/lib/nx/share/rgb
/usr/lib/nx/share/rgb is owned by nxclient 3.5.0.7-2
This file was in old version of xorg here /usr/share/X11/rgb, but not now.
May be you have compat link or file, try to search rgb file in /usr/lib and /usr/share
Now it should be only in nxclient package
fonts:
I wrote it's not optimal, not broken. Main problem it's missed /usr/share/fonts/local
If you set custom font from /usr/share/fonts/local for xterm, it falls back to standard fixed font.
Try to set this in .Xdefaults (you need terminus-fonts package)
XTerm.VT100.font: -xos4-terminus-medium-r-normal--14-140-72-72-c-80-iso10646-1
Any change in files applies after restart of nxclient
As I know old type X applications use client side resources, but get path from server.
NX uses quite old X components, that's why no problem to run locally with recent Xorg version
This file is located on the client.
pacman -Qo /usr/lib/nx/share/rgb
/usr/lib/nx/share/rgb is owned by nxclient 3.5.0.7-2
This file was in old version of xorg here /usr/share/X11/rgb, but not now.
May be you have compat link or file, try to search rgb file in /usr/lib and /usr/share
Now it should be only in nxclient package
fonts:
I wrote it's not optimal, not broken. Main problem it's missed /usr/share/fonts/local
If you set custom font from /usr/share/fonts/local for xterm, it falls back to standard fixed font.
Try to set this in .Xdefaults (you need terminus-fonts package)
XTerm.VT100.font: -xos4-terminus-medium-r-normal--14-140-72-72-c-80-iso10646-1
Any change in files applies after restart of nxclient
http://www.mepis.org/docs/en/index.php?title=NX_Server#Fix_for_MEPIS_6.x
Maybe we don't need to hardpatch all possible repo and AUR font paths.
A good hint in our wiki and/or some hint in the node.conf file should do the same.
Problem solved
Thanks