Bug#309012: 309012

2006-10-08 Thread Dirk Eddelbuettel
On 7 October 2006 at 15:26, Andreas J Guelzow wrote: | We are experiencing a similar issue and may have some light to shed on | the issue (especially for others that may experience it to). | | We are running ltsp thin-clients connecting via xdmcp to a debian | unstable amd64 machine. We

Bug#309012: Follow-up on R/amd64 cannot find fonts in some cases (Was: Bug#309012: 309012(

2006-10-08 Thread Dirk Eddelbuettel
Peter, Kurt, Brian, Here is a belated comment from an R user on amd64 experiencing font problems as described in an earlier bug report by Ryan, and a suggested way to fix the issue. The full (older) discussion of the problem is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309012

Bug#309012: Follow-up on R/amd64 cannot find fonts in some cases (Was: Bug#309012: 309012(

2006-10-08 Thread Dirk Eddelbuettel
On 8 October 2006 at 10:04, Ryan Lovett wrote: | On Sun, Oct 08, 2006 at 10:45:28AM -0500, Dirk Eddelbuettel wrote: | Peter, Kurt, Brian, | | Here is a belated comment from an R user on amd64 experiencing font problems | as described in an earlier bug report by Ryan, and a suggested way to

Bug#309012: Follow-up on R/amd64 cannot find fonts in some cases (Was: Bug#309012: 309012(

2006-10-08 Thread Ryan Lovett
On Sun, Oct 08, 2006 at 10:45:28AM -0500, Dirk Eddelbuettel wrote: Peter, Kurt, Brian, Here is a belated comment from an R user on amd64 experiencing font problems as described in an earlier bug report by Ryan, and a suggested way to fix the issue. The full (older) discussion of the

Bug#309012: Follow-up on R/amd64 cannot find fonts in some cases (Was: Bug#309012: 309012)

2006-10-08 Thread Andreas J. Guelzow
A moment ago I wrote: well I have the following: (I removed some output lines from xset q that are clearly irrelevant.) [EMAIL PROTECTED]:~$ xset q Font Path:

Bug#309012: 309012

2006-10-07 Thread Andreas J Guelzow
We are experiencing a similar issue and may have some light to shed on the issue (especially for others that may experience it to). We are running ltsp thin-clients connecting via xdmcp to a debian unstable amd64 machine. We occasionally got the same error. It turned out that the error occurs