On Sun, 26 Mar 2006, Hamish Moffatt wrote:
> Interesting. So is your X server 32-bit or 64-bit? So you are sshing TO
> the amd64 machine, from what other machine?
The other machine is a up-to-date 32-bit Debian testing/unstable machine.
There is no problem with running xpdf X-forwarded in the ot
On Sat, Mar 25, 2006 at 06:52:51PM -0500, D. Hilley wrote:
> On Mon, 13 Mar 2006, Hamish Moffatt wrote:
> > It can't be a general amd64 problem as I'm running amd64 myself and
> > using Xpdf regularly.
>
> Oh boy, now I feel silly because I left out an important detail. I could
> have sworn I stat
On Mon, 13 Mar 2006, Hamish Moffatt wrote:
> It can't be a general amd64 problem as I'm running amd64 myself and
> using Xpdf regularly.
Oh boy, now I feel silly because I left out an important detail. I could
have sworn I stated it in my original message, but this occurs when
X-forwarded over ssh
On Sun, Mar 12, 2006 at 04:46:14PM -0500, D. Hilley wrote:
> Subject: xpdf segfault on amd64
> Package: xpdf-reader
> Version: 3.01-7
> Severity: important
>
> Hi, I'm running testing/unstable amd64 debian and xpdf segfaults for
> me every time at startup. I'm not sure if this is actually an xpdf
Subject: xpdf segfault on amd64
Package: xpdf-reader
Version: 3.01-7
Severity: important
Hi, I'm running testing/unstable amd64 debian and xpdf segfaults for
me every time at startup. I'm not sure if this is actually an xpdf
bug or perhaps in some X library. I saw a post on the
linux.debian.port
5 matches
Mail list logo
