oops. Just found out the same cause as Sebastian said, somehow I miss
his thread when I read the bug. I will just keep using vncserver 32bit then.
Sorry for any inconvenience.
Ola Lundqvist wrote:
Hi
On Mon, May 01, 2006 at 02:08:18PM +0800, Hing-Wah Wan wrote:
Hi,
I'm able to reproduce it on stable on amd64 using vncserver or
tightvncserver.
The thread:
http://lists.debian.org/debian-amd64/2004/11/msg00076.html also showed
that the problem also occur on vnc 3.3.x
I'm aware that the problem occur on vnc 3. I was not aware that it
happen on tightvnc as well though.
I guess similiar patch can be applied on vnc 3.3?
http://lists.debian.org/debian-amd64/2005/12/msg00255.html
No. This is unfortunatly a patch to make it compile, not to make it
work.
Regards,
// Ola
Ola Lundqvist wrote:
Hi
On Sun, Apr 30, 2006 at 06:52:21PM +0000, Hing-Wah Wan wrote:
Hi,
Please check the thread:
http://lists.debian.org/debian-amd64/2004/11/msg00064.html
Hope the fix will get into the official package.
I do not really follow you. This discussion is about vnc4 and
as far as I know that work just fine on amd64.
Or have I misunderstood something?
Regards,
// Ola
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
