Your message dated Mon, 12 Feb 2007 22:33:48 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Oops, not an rdesktop problem at all.
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: rdesktop
Version: 1.5.0-1
Severity: important

I try to connect to a WinXP-system. The desktop comes up, at it works
for a few seconds, but then
the connection freezes: the window is no longer updated.  rdesktop
isn't dead itself, I can still
change to full-screen or back (though the window becomes blank then).

If I close rdesktop, I have no problem connecting again -- to get
another few seconds.

Could this be a problem with the amd64 build of rdesktop?  It worked
fine on my old 32-bit computer.

FYI, the WinXP is a 32 bit system, and I connect via PPTP VPN.

If you have some ideas of what to look for, I'll be happy to help
tracking down the problem.


-- System Information:
Debian Release: 4.0
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)

Versions of packages rdesktop depends on:
ii  libc6                       2.3.6.ds1-10 GNU C Library: Shared libraries
ii  libssl0.9.8                 0.9.8c-4     SSL shared libraries
ii  libx11-6                    2:1.0.3-5    X11 client-side library

rdesktop recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
I've done some further testing, and it turns out that the MTU on my
eth0 was somehow set to 576.  Changing the MTU to 1500 solved the
problem.

I'm sorry for reporting this as a bug against rdesktop.  I should have
thought of an MTU-problem from the start.  Now, I'll go hunting for
the reason for this strange MTU...


Rune

--- End Message ---

Reply via email to