Terminal Server Client Error

Bug #181428 reported by francis habets on 2008-01-09
58
This bug affects 8 people
Affects Status Importance Assigned to Milestone
tsclient (Ubuntu)
Undecided
Unassigned

Bug Description

ERROR: Failed to open keymap be
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

francis habets (fhabets) wrote :

I receive this error message when trying to connect via RDP with a Windows server 2003

I also get a similar error message

EliCoten (launchpad-elicoten) wrote :

I also get a similar error message:
 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 <variable number>

I have a Windows XP server. I find that at 256 colour it connects fine, and at 640x480 it usually connects fine, except in 15bit color. In 24bit color [640x480] I get an error message after I close it about server not supporting 24 bit color - falling back to 16bit. Don't know if this is related.

If I try 800x600 or greater it seems to always crash, except in 256 color.

ktp420 (ktp420) wrote :

Try changing the protocol from RDP to RDPv5.

francis habets (fhabets) wrote :

changing the protocol from RDP to RDPv5 changed nothing for me (same error message).
This is a recurrent problem I have with the connection to a windows 2003 server on different installations, every few weeks I have this problem and suddenly it works again. The last time I had the problem I just changed the "Client hostname" in the connection box and the connection works.

Anton (apogif) wrote :

Similar problem.

When closing Terminal Server Client window, I get an error message:
"An error has occured.
reconnect in ... sec
Details:
Autoselected keyboard map en-us
NOT IMPLEMENTED: System pointer message 0x7f00
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 0x0
Serial number of failed request: 31165
Current serial number in outpu stream: 31165"

After changing from RDP to RDPv5 closing a window leads to this error message:
"An error has occured.
reconnect in ... sec
Details:
Autoselected keyboard map en-us"

Screen size=640x480, Color depth=256 colors

Anton (apogif) wrote :

Sorry, first message was:
"An error has occured.
reconnect in ... sec
Details:
Autoselected keyboard map en-us
NOT IMPLEMENTED: System pointer message 0x7f00
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: 31165
Current serial number in output stream: 31165"

ChrisL (chrislampson) wrote :

Similar problem. Always connects fine.
Tested on:
- multiple resolutions and colors.
- Windows XP Pro SP3
- Windows Server 2003 SP2

Upon disconnect:

An error has occured.

---Details---
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: 9043
Current serial number in output stream: 9043
---
(Serial and Current serial always change)

Also see this bug:
https://bugs.launchpad.net/ubuntu/+source/tsclient/+bug/203830

Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 or 9.04?

Changed in tsclient:
status: New → Incomplete
catinsnow (catinsnow) wrote :

Yes,I still have this problem in 8.10. I even cannot connect the win2003 server with this error.

Anton (apogif) wrote :

Upgraded to 8.10. Having same symptoms as described above...

Denis Walrave (deniswalrave) wrote :

Same problem (doesn't work at all, same error message):
Kubuntu 8.10
lenovo R61 laptop
intel graphic chipset
intel driver

Denis Walrave (deniswalrave) wrote :

$ tsclient

** (tsclient:19322): WARNING **:
Autoselected keyboard map fr
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: 56
  Current serial number in output stream: 56

(tsclient:19322): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.18.2/gobject/gsignal.c:2384: instance `0x88d08d8' has no handler with id `1070'

mati (mateusz505) wrote :

I`ve got exactly the same error.

nutmac (peanutjelly) wrote :

I was able to resolve this issue by manually setting "en-us" (replace with whatever code you are using, such as "be" or "fr") under "Use the following keyboard language" at Local Resource tab.

nattygreg (gregory-brown) wrote :

always set parameters for ts client it does not work like windows just click and go set keyboard preference, set resolution to that of the machine you are connecting to, always use 256 colors, if the machine is really old use 16 bit colours and finally use RDP V5 instead of rdp will not connect if you R trying to connect to server 2003 will always want the most secure connection

Ryan Maki (ryan.maki) wrote :

Still affects me on 9.04.

I have started a profile from scratch, I have copied RDP files from other machines, I have tinkered with every available setting in the RDP file directly. When I first installed 9.04 I entered a new profile and connected just to the termserver with no errors. However, several days later I need to connect and I get the same errors I got in 8.10.

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: 56
  Current serial number in output stream: 56

Setting the keymap to "EN" "en" "us" "en_us" all failed with the same error. I have even deleted the ~/.tsclient folder to attempt to start from scratch, like I did just after installing 9.04 but to no avail.

Ryan Maki (ryan.maki) wrote :

I have attempted to connect to the termserver in question with rdesktop and I receive an error message about License Server. This may be the _actual_ error message, and tsclient may be misreporting the error.

$ rdesktop termserver
Autoselected keyboard map en-us
disconnect: No license server available.

I don't think the keymap is the problem, I think it's actually a lack of licenses, but that the error message is incorrectly reporting keymap. This may help to explain why it seems to be an intermittent problem. Connecting with RDP on Windows actually gives a similar error about a missing license server. I have my IT folks looking in to the problem.

Ryan Maki (ryan.maki) wrote :

Confirmed that when IT fixed the rdesktop "No license server available" error that tsclient was also able to connect. When exiting the session a tsclient dialog indicates an error has occurred with the following error:

NOT IMPLEMENTED: System pointer message 0x7f00
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: 5547
  Current serial number in output stream: 5547

And attempts to reconnect after 30 seconds. It appears to me from this investigation that tsclient is catching errors that are not affecting the session setup, and others (such as my license server problem) are going unreported, thus masking the problem.

Djno (jnl) wrote :

Had same problem connecting to a Windows 2008 TS with rdesktop 1.6.0 on 8.04.

Autoselected keyboard map fr
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: 50
  Current serial number in output stream: 50

By modifying the Terminal Services licensing mode on the server (from CAL per Device to CAL per User) this problem is gone and I can connect normally to the Terminal Server.

Hope this helps.

tkelsey (kelsey-tim) wrote :

To fix this change your display to 1024x768 and keep it on RDP. This will allow you to remote into a windows machine.

The only problem now is when you close the client, you still get the error, but at least you are able to use the program now.

Bugiman (farouk) wrote :

For those of you who are interested, I fixed this by choosing Full Screen Mode. I did not receive the error anymore.

Cengiz Can (cengizcan) wrote :

Using fully updated (stable only) Ubuntu 9.04 amd64.
Connecting to a machine with XP SP2

Using default settings produces this error with an interval of 10 seconds.

However, working with
-- RDPv5
-- 256 colors
-- Full screen

does not produce this error.

REMEMBER: You can exit Fullscreen with CTRL+ALT+ENTER

ray (rayfitzharris) wrote :

I still have this issue also, none of the above suggestions work for me, sometimes it produces the error, but most times the screen goes black for a second and then returns to the connection screen.
I can connect to the server (winxp pro) no problem from windows boxes, and have connected from the ubuntu machine before. I'm running eeebuntu 3.0 (9.10)

This is a constant problem for me as well and it was present in 9.04, 9.10 and now 10.04. My current Ubuntu build is:

Ubuntu 10.04 LTS \n \l

Linux box1 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010 x86_64 GNU/Linux

The problem is not present when connecting to Windows 2008 servers, only Windows 2003 servers. I'm using RDPv5 in the tsclient settings. It's a very annoying problem. I connect to a Windows 2003 server and the window comes up. Sometimes the problem occurs right away in that I cannot login because of network issues (I guess, with the tsclient) and the session freezes and disconnects. Sometimes I can login but the session freezes just after that and finally disconnects. If I use a Windows client/OS these issues are never present on any server I connect to with RDP so it seems as if something is broken with the Ubuntu package(s).

I have tried fiddling with the tsclient/rdesktop options to no avail.

I run tsclient -vvv from the CLI and here's what's in the console for a session that fails.

cd@box1:~$ tsclient -vvv

(tsclient:17124): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:3079: signal name `depressed' is invalid for instance `0x1988800'

(tsclient:17124): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.0/gobject/gsignal.c:3079: signal name `depressed' is invalid for instance `0x1988800'

** (tsclient:17124): WARNING **:
Autoselected keyboard map en-us
WARNING: Remote desktop does not support colour depth 24; falling back to 16
ERROR: recv: Connection reset by peer

David Oftedal (rounin) wrote :

I have this same bug with the two cryptic error codes being 55 instead of 48.

krdc has also ceased to work, abruptly disconnecting in the same manner, so it's reasonable to believe krdc is affected by the same bug.

David Oftedal (rounin) wrote :

The problem occurred specifically with the server windows.ifi.uio.no belonging to the University of Oslo, and has been experienced and described by another user here:

http://dragly.org/2010/08/31/internal-licensing-error/

The solution I used was to delete, recreate and chattr +i the licence file found in ~/.rdesktop, so that it remains empty and cannot be changed.

David Oftedal (rounin) wrote :

To modify my earlier statement somewhat:

The problem with the X Error of failed request: BadAtom (invalid Atom parameter) and so on and so forth is alleviated by changing protocols from "RDP" to "RDPv5".

The bug that THEN occurs, and the solution for that, is described in the above URL ( http://dragly.org/2010/08/31/internal-licensing-error/ ).

As krdc apparently defaults to RDPv5 somehow, solving the second problem also solves the first.

Jonathan Thomas (echidnaman) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

Changed in kdenetwork (Ubuntu):
status: New → Invalid

Any real progress on the cause of this? I would love to have a fix provided since this condition occurs at the most inopportune times. It is interesting that connecting to Windows 2008 servers over RDP never results in this error (for me at least). Connecting to Windows 2003 servers is sometimes flawless and other times I have to disconnect and reconnect repeatedly to finally get a usable session/connection.

98cwitr (brettm) wrote :

I am also having this problem when trying to connect to a Server 2008 box from 10.10. Connecting to Server 2003 boxes works fine.

Jean Visser (visserman365) wrote :

This may be due to the encryption type used by the rdp server.

On server 2003, under 'Administrative tools', select 'Terminal service configuration'

Select the 'Connections' folder when the console appears, the on the right hand pane select 'RDP-Tcp', right click and select 'Properties'

When the properties page appears, go to the 'General' tab and see what option is set under 'Security layer'. 'SSL' does not work for me, but if I set it to 'Negotiate' it does connect.

I can only assume that the rdesktop client knows nothing about ssl and uses the standard rdp security (I have selected rdvpv5 and it still did not work).

I recommend poking around the other tabs, you'll be able to set lots of session option, most usefully under the 'Client Settings' tab.

Haven't tried this with Server 2k8, but I suppose it similar. Windows XP does not seem to be configurable in this regard.

Cheers,
Fish

Changed in grdesktop (Ubuntu):
status: New → Incomplete
Changed in grdesktop (Ubuntu):
status: Incomplete → Confirmed
Changed in tsclient (Ubuntu):
status: Incomplete → Confirmed
affects: tsclient (Ubuntu) → remmina (Ubuntu)
Changed in grdesktop (Ubuntu):
status: Confirmed → Invalid
no longer affects: remmina (Ubuntu)
no longer affects: kdenetwork (Ubuntu)
no longer affects: grdesktop (Ubuntu)
Launchpad Janitor (janitor) wrote :

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

tsclient is no longer supported in a Desktop release.

affects: tsclient → tsclient (Ubuntu)
Changed in tsclient (Ubuntu):
status: New → Invalid
Changed in tsclient (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions