If cairo is upgraded past 1.10 NX server no longer displays characters in menu bars and many other applications. Backing Cairo back to 1.10 resolves. No error messages or anything like that appear to be logged so I'm not sure what in net-misc/nx is triggering the bug when used with cairo 1.12 or greater. Reproducible: Always Steps to Reproduce: 1. Install a higher cairo version than 1.10* 2. Connect to NX server 3. missing text Actual Results: nx client does not display some text Expected Results: display text
Should be assigned to nx@gentoo.org I seem to have lost assignment privs.
Setting "downgrade dependencies" is extremely bad form - the real problem should be fixed instead.
I am also seeing this issue. I will try downgrading temporarily.
I believe this could be the same or related issue: http://lists.berlios.de/pipermail/x2go-dev/2012-May/003963.html
It probably is. Do you have the problem only when reconnecting to a running session (as it is decribed in x2go mailing archives)? On my test install, simple sessions work fine with >=net-misc/nx-3.5.0.14, which has the patches for partial cairo-1.12 support (Gentoo uses the nx libs from x2go now) Sadly I'm not sure we can do more on our side (restricting to <cairo-1.12 is not a viable option in the long term)
I see it both on new connections and also when resuming. It does seem similar to the issue reported on the nx2go archives but it appears that the issue was resolved there and as far as I can tell the Gentoo ebuild also has these fixes so I'm puzzled. Perhaps there were additional changes in Cairo since that have re broken the fix.
Good news, apparently x2go folks found a fix: http://code.x2go.org/gitweb?p=nx-libs.git;a=blob;f=debian/patches/204_nxagent_repaint-solidpict.full.patch There is a new nx-libs tarball available, I'll test and add it next week (my commit box is down for the week-end)
3.5.0.15 in tree now, can you test and see if this fixes it for you? I'll leave the bug open in the meantime
Stabling is underway for this version in bug #445766, let's continue on bug #441878 if required. Marking this one fixed