tightvnc sends bad request causing rdesktop and/or remmina to crash with Unity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tightvnc (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have now set up a local precise machine.
I use xrdp to connect to the new box.
On the old machine, I use tsclient in lucid.
All is fine and dandy till I try to launch an application in the precise screen.
At that moment, tsclient stops, and tries a reconnect.
Below the logging after starting tsclient from the command line.
** (tsclient:11817): WARNING **:
Autoselected keyboard map en-us
ERROR: channel_register
WARNING: Initializing sound-support failed!
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 23 (X_GetSelection
Atom id in failed request: 0x0
Serial number of failed request: 29974
Current serial number in output stream: 29974
** (tsclient:11817): WARNING **:
Autoselected keyboard map en-us
ERROR: channel_register
WARNING: Initializing sound-support failed!
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 23 (X_GetSelection
Atom id in failed request: 0x0
Serial number of failed request: 30804
Current serial number in output stream: 30804
(tsclient:11817): GLib-GObject-
** (tsclient:11817): WARNING **:
Autoselected keyboard map en-us
ERROR: channel_register
WARNING: Initializing sound-support failed!
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 23 (X_GetSelection
Atom id in failed request: 0x0
Serial number of failed request: 33698
Current serial number in output stream: 33698
(tsclient:11817): GLib-GObject-
affects: | tsclient (Ubuntu) → rdesktop (Ubuntu) |
rdesktop shipped with precise crashes in a similar fashion on using rdp4
Autoselected keyboard map en-us Owner)
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 23 (X_GetSelection
Atom id in failed request: 0x0
Serial number of failed request: 39220
Current serial number in output stream: 39220
on using rdesktop of precise to log in to precise with rdp5 (the default), rdesktop stops without logging just after the unity screen is built up on the screen.
Afterthought: If the atom ID of 0 is indeed an illegal value, this bus should not be filed against the rdesktop, but rather against the server in precise.