Terminal Server Client crashes when disconnecting correctly

[wentbackward]

Binary package hint: tsclient

Connected remotely via VPN to a Windows XP box. That box is actually a VMWare based VM.

Simply select START-->Disconnect and I believe that nothing untoward is happening, perhaps tsclient is not correctly handling the disconnect.

ProblemType: Crash
Architecture: i386
Date: Thu Apr 5 15:32:59 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/rdesktop
Package: rdesktop 1.5.0-1build1
PackageArchitecture: i386
ProcCmdline: rdesktop -Thkgitdw3027\ -\ Terminal\ Server\ Client -ugreshap -dCLSAGEM -rsound:local -b hkgitdw3027
ProcCwd: /home/paul
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rdesktop
StacktraceTop:
 XPutImage () from /usr/lib/libX11.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux paul-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

[Apport retracing service (apport)]

StacktraceTop:_XrmInternalStringToQuark (name=<value optimized out>, len=48234501, sig=138255248, permstring=0) at ../../src/Quarks.c:340
?? ()
?? ()
?? ()
?? ()

[Jonh Wendell (wendell)]

This is not a tsclient issue, but a rdesktop one.

[Peter Matulis (petermatulis)]

On Feisty I have confirmed this behaviour when connecting to WXP Pro system with rdesktop 1.5.0 / tsclient 0.148.

** (tsclient:7987): WARNING **:
Autoselected keyboard map en-us
X Error of failed request: BadAtom (invalid Atom parameter)
  Major opcode of failed request: 23 (X_GetSelectionOwner)
  Atom id in failed request: 0x0
  Serial number of failed request: 3853
  Current serial number in output stream: 3853

[nesman89 (lester-odev)]

I can confirm this issue while connecting to windows server 2003. Happens everytime when I close the RDP connection from the server.

[Peter Matulis (petermatulis)]

You can tell the client to use protocol v5.

General-> Protocol: RDPv5

[Roberto Dhios (radhios)]

I can confirm that this problem occur when using protocol RDP or RDPv5 on XP or W2K boxes.

[nynexman4464 (alex-alexrock)]

Still seems to be happening in gutsy.

[Eugene van der Merwe (eugene-snowball)]

I have the same problem happening on Hardy:

X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 23 (X_GetSelectionOwner)
Atom id in failed request: 0x0
Serial number of failed request: 4940
Current serial number in output stream: 4908

Switched to gnome-rdp

[zabzoo (zabzoo)]

Same problem On Hardy when connecting to Windows XP Service Pack 3

XXX@XXX:~/.ssh$ rdesktop -4 XXXXXXXXXXXXX
X Error of failed request: BadAtom (invalid Atom parameter)
  Major opcode of failed request: 23 (X_GetSelectionOwner)
  Atom id in failed request: 0x0
  Serial number of failed request: 48
  Current serial number in output stream: 48

or with rdesktop without the -4

Fresh installation; all i did was install vnc4server - not sure if that had anything to do with it!

[san_ubuntu (gupta-sandeep)]

Same problem on Intrepid when trying to connect to windows 2003 server.

[san_ubuntu (gupta-sandeep)]

The problem seems to appear across all gnome-rdp, krdc, and rdesktop. However rebooting the remote server and the local machine fixed the problem.

[Asermar (alexis-okodex)]

Hi,
I have the same problem with Karmic and Intrepid.
The problem was resolved updating de nvidia driver of the windows computer.

bye.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Not reproducible in Trusty to Vista (Windows XP is EoL as per http://www.microsoft.com/en-us/windows/enterprise/end-of-support.aspx , and tsclient is no longer available in a supported Desktop release).