Thanks for that info - one less frustration to contend with...
On Wed, Jul 1, 2009 at 4:50 AM, Bassu Khan <email address hidden> wrote:
> joebodo, I've been seeing this problem for almost two years the time since
> when I switched to Debian/Ubuntu.
> This occurs when you'll keep your rdesktop windows minimized for about
> 20-30 mins. This is something I feel that Gnome/Rdesktop does and not the
> client machines you're connecting to. I've tried a lot to find a reason for
> this rdesktop behaviour but couldn't even though at one I suspected Compiz
> causing that!
>
> And a more interesting thing is that, this sometimes happens with other
> Linux distros as well.
> Again, if you'll keep your window maximized or just active under the
> current top window of any application, you'll likely not encounter the
> issue.
>
> --
> rdesktop freezes shortly after successful connection
> https://bugs.launchpad.net/bugs/217868
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “rdesktop” package in Ubuntu: Incomplete
> Status in “rdesktop” package in Debian: New
>
> Bug description:
> In Gutsy and Hardy, I am able to connect to the server via RDP. Shortly
> (30sec-1min) after login, the connection freezes---the pointer still
> responds, but I am unable to see the results of any mouse clicks or
> keypresses. If I kill the client and reconnect, I see that the mouse clicks
> and keypresses were being sent to the remote server. There are no
> side-effects on other X applications---everything continues to work except
> for rdesktop.
>
> This behavior was identical under Gutsy and on two different Hardy
> machines, regardless of network interface. I tried the Gutsy rdesktop
> package and also tried compiling the latest rdesktop cvs, all with the same
> results. However it worked fine under Dapper.
>
> I normally invoke rdesktop as
>
> rdesktop -a 8 -z -P -U username server
>
> Dropping -z or -P makes the connection quit faster, as does using a higher
> color depth.
>
> This thread
>
> http://ubuntuforums.org/showthread.php?p=4709775
>
> discusses what appears to be the same problem experienced by other users.
> Please contact me if further information is needed to diagnose.
>
Thanks for that info - one less frustration to contend with...
On Wed, Jul 1, 2009 at 4:50 AM, Bassu Khan <email address hidden> wrote:
> joebodo, I've been seeing this problem for almost two years the time since /bugs.launchpad .net/bugs/ 217868 --everything continues to work except ubuntuforums. org/showthread. php?p=4709775
> when I switched to Debian/Ubuntu.
> This occurs when you'll keep your rdesktop windows minimized for about
> 20-30 mins. This is something I feel that Gnome/Rdesktop does and not the
> client machines you're connecting to. I've tried a lot to find a reason for
> this rdesktop behaviour but couldn't even though at one I suspected Compiz
> causing that!
>
> And a more interesting thing is that, this sometimes happens with other
> Linux distros as well.
> Again, if you'll keep your window maximized or just active under the
> current top window of any application, you'll likely not encounter the
> issue.
>
> --
> rdesktop freezes shortly after successful connection
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “rdesktop” package in Ubuntu: Incomplete
> Status in “rdesktop” package in Debian: New
>
> Bug description:
> In Gutsy and Hardy, I am able to connect to the server via RDP. Shortly
> (30sec-1min) after login, the connection freezes---the pointer still
> responds, but I am unable to see the results of any mouse clicks or
> keypresses. If I kill the client and reconnect, I see that the mouse clicks
> and keypresses were being sent to the remote server. There are no
> side-effects on other X applications-
> for rdesktop.
>
> This behavior was identical under Gutsy and on two different Hardy
> machines, regardless of network interface. I tried the Gutsy rdesktop
> package and also tried compiling the latest rdesktop cvs, all with the same
> results. However it worked fine under Dapper.
>
> I normally invoke rdesktop as
>
> rdesktop -a 8 -z -P -U username server
>
> Dropping -z or -P makes the connection quit faster, as does using a higher
> color depth.
>
> This thread
>
> http://
>
> discusses what appears to be the same problem experienced by other users.
> Please contact me if further information is needed to diagnose.
>