tsclilent in intrepid does not enable sound

[Martin G Miller]

Binary package hint: tsclient

32 bit Ubuntu 8.10 beta as of 6 October, 2008. Using terminal server client to connect to a Windows XP pro sp2 machine via RDPv5 will not play sound over the connection. It does work correctly in Ubuntu 8.04.1
On disconnecting the session the following error is generated:

Error: Channel register
Warning: Initializing Sound support failed!
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: 828
Current serial number in output stream 828

Note, the number at the end of the last 2 lines changes each time you exit.

In addition to this, the desktop wallpaper on the remote machine is now displayed over the remote desktop session. This did not used to be the case. I don't see any way to turn this feature off. It does tend to slow down drawing the screen, especially over an internet connection.

What I expected to happen:
1) Sound support should be enabled.
2) Should not display the remote computers desktop wallpaper by default.

What actually happened:
1) No sound during the session
2) The above error message is displayed on log off
3) The remote computers desktop wallpaper is displayed, slowing down the responsiveness of the session.

[Matt Satorius (matt-sators)]

I also am experiencing the same issue with tsclient version 0.150-1ubuntu3 installed on two different machines attempting to connect to a Vista server.

[Martin G Miller (mgmiller)]

Because this bug results in an error message on disconnect, it attempts to reconnect after 30 seconds. This makes it unusable in my office where I rely on ts client from 4 different work stations to RD into a single logon in a windows server. I rely on the new connection to end the one from the previous work station.

This works perfectly in 8.04.1. In the new version in 8.10, I would be kicked off my connection after 30 seconds, when the old workstation attempts to log in again.

[mattathome (mschedler49)]

I found that by switching to RDPv5 everything worked fine... helpful?

[mattathome (mschedler49)]

Oops... should have said that I got the same error as above with RDP but changing to RDPv5 fixed it.