Remote Desktop error when connect to the Ubuntu LTS 16.04

[Zhesen Zhang]

Using the windows remote desktop to connect to the Ubuntu LTS 16.04, the session failed.

The .xsession-errors log as followings,

#cat .xsession-errors
Xsession: X session started for at Fri May 6 17:52:57 PDT 2016
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 109 (X_ChangeHosts)
  Value in failed request: 0x5
  Serial number of failed request: 6
  Current serial number in output stream: 8
localuser:ubuntu being added to access control list
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 109 (X_ChangeHosts)
  Value in failed request: 0x5
  Serial number of failed request: 6
  Current serial number in output stream: 8
/etc/xrdp/startwm.sh: 3: [: x: unexpected operator

#cat /proc/version_signature
Ubuntu 4.4.0-21.37-generic 4.4.6

##lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=16c28cbc-e675-4e08-9672-32b766cdd90a
InstallationDate: Installed on 2015-09-08 (241 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: HP ProLiant DL360 Gen9
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=1036285c-b89e-4d97-b5a5-199699b2651c ro
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-05-05 (1 days ago)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 11/03/2014
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL360 Gen9
dmi.sys.vendor: HP

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1579282

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Zhesen Zhang (zhang352)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-wily/

[Zhesen Zhang (zhang352)]

You are welcome!

Just first time using the Windows remote desktop to connect the Ubuntu, did not use the Windows remote desktop before the upgrade.

Upgraded the kernel to 4.6 based on the above link and still no luck. :-(

#uname -a
Linux ipod-kvm12 4.6.0-040600rc7-generic #201605081830 SMP Sun May 8 22:32:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

#cat .xsession-errors
Xsession: X session started for at Mon May 9 12:12:13 PDT 2016
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 109 (X_ChangeHosts)
  Value in failed request: 0x5
  Serial number of failed request: 6
  Current serial number in output stream: 8
localuser:ubuntu being added to access control list
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 109 (X_ChangeHosts)
  Value in failed request: 0x5
  Serial number of failed request: 6
  Current serial number in output stream: 8
/etc/xrdp/startwm.sh: 3: [: x: unexpected operator

[Zhesen Zhang (zhang352)]

Deleted previous upgraded version of Xenial and reinstalled the Xenial and connected by using Windows remote desktop, it is still the errors.

#cat .xsession-errors
openConnection: connect: No such file or directory
cannot connect to brltty at :0
Xsession: X session started for at Tue May 10 11:29:18 PDT 2016
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 109 (X_ChangeHosts)
  Value in failed request: 0x5
  Serial number of failed request: 6
  Current serial number in output stream: 8
localuser:ubuntu being added to access control list
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 109 (X_ChangeHosts)
  Value in failed request: 0x5
  Serial number of failed request: 6
  Current serial number in output stream: 8
openConnection: connect: No such file or directory
cannot connect to brltty at :0

[Zhesen Zhang (zhang352)]

Upgraded to Kernel to 4.6, the same failure.

[abdul_zummerwala (abdul-zummerwala)]

I am also facing the same problem... No posts on its solution so far on Google

[abdul_zummerwala (abdul-zummerwala)]

Have the log from /var/log/xrdp-sesman.log if useful

[20160512-17:26:58] [CORE ] starting sesman with pid 5357
[20160512-17:26:58] [INFO ] listening...
[20160512-17:32:17] [INFO ] shutting down sesman 1
[20160512-17:32:17] [CORE ] starting sesman with pid 11132
[20160512-17:32:17] [INFO ] listening...
[20160512-17:32:32] [INFO ] scp thread on sck 7 started successfully
[20160512-17:32:32] [INFO ] ++ created session (access granted): username postgres, ip 192.168.15.60:17204 - socket: 7
[20160512-17:32:32] [INFO ] starting Xvnc session...
[20160512-17:32:33] [INFO ] starting xrdp-sessvc - xpid=11143 - wmpid=11142
[20160512-17:32:33] [INFO ] ++ terminated session: username postgres, display :10.0, session_pid 11140, ip 192.168.15.60:17204 - socket: 7
[20160512-17:32:42] [INFO ] scp thread on sck 7 started successfully
[20160512-17:32:42] [INFO ] ++ created session (access granted): username postgres, ip 192.168.15.60:17204 - socket: 7
[20160512-17:32:42] [INFO ] starting Xvnc session...
[20160512-17:32:42] [INFO ] starting xrdp-sessvc - xpid=11196 - wmpid=11195
[20160512-17:32:42] [INFO ] ++ terminated session: username postgres, display :10.0, session_pid 11193, ip 192.168.15.60:17204 - socket: 7
[20160512-17:39:29] [INFO ] shutting down sesman 1
[20160512-17:39:30] [CORE ] starting sesman with pid 11507
[20160512-17:39:30] [INFO ] listening...
[20160512-17:39:43] [INFO ] scp thread on sck 7 started successfully
[20160512-17:39:43] [INFO ] ++ created session (access granted): username postgres, ip 192.168.15.60:17270 - socket: 7
[20160512-17:39:43] [INFO ] starting Xvnc session...
[20160512-17:39:43] [INFO ] starting xrdp-sessvc - xpid=11516 - wmpid=11515
[20160512-17:39:44] [INFO ] ++ terminated session: username postgres, display :10.0, session_pid 11513, ip 192.168.15.60:17270 - socket: 7
[20160512-17:39:53] [INFO ] scp thread on sck 7 started successfully
[20160512-17:39:53] [INFO ] ++ created session (access granted): username postgres, ip 192.168.15.60:17270 - socket: 7
[20160512-17:39:53] [INFO ] starting Xvnc session...
[20160512-17:39:54] [INFO ] starting xrdp-sessvc - xpid=11589 - wmpid=11588
[20160512-17:39:55] [INFO ] ++ terminated session: username postgres, display :10.0, session_pid 11585, ip 192.168.15.60:17270 - socket: 7
[20160512-17:44:21] [INFO ] scp thread on sck 7 started successfully
[20160512-17:44:22] [INFO ] ++ created session (access granted): username postgres, ip 192.168.15.60:17270 - socket: 7
[20160512-17:44:22] [INFO ] starting Xvnc session...
[20160512-17:44:22] [INFO ] starting xrdp-sessvc - xpid=11703 - wmpid=11702
[20160512-17:44:22] [INFO ] ++ terminated session: username postgres, display :10.0, session_pid 11700, ip 192.168.15.60:17270 - socket: 7
[20160512-17:44:37] [INFO ] scp thread on sck 7 started successfully
[20160512-17:44:37] [INFO ] ++ created session (access granted): username postgres, ip 192.168.15.60:17270 - socket: 7
[20160512-17:44:38] [INFO ] starting Xvnc session...
[20160512-17:44:38] [INFO ] starting xrdp-sessvc - xpid=11763 - wmpid=11762
[20160512-17:44:38] [INFO ] ++ terminated session: username postgres, display :10.0, session_pid 11760, ip 192.168.15.60:17270 - socket: 7
[20...

[penalvch (penalvch)]

Jason:
1) Do you have any PPAs installed?
2) Could you please advise how you setup xrdp?

To advise, I'm able to xrdp into 16.04 from Windows/Ubuntu with no problem, but the way I set it up may be quite different.

[Zhesen Zhang (zhang352)]

Hi Christopher,

I did not have any PPAs installed and I just use the default setting of the xrdp, I installed the default xrdp package from default Ubuntu repo.

Can you share your configuration?

Thanks!

[penalvch (penalvch)]

Jason, I setup xrdp via:
https://help.ubuntu.com/community/xrdp

However, as xrdp as implemented doesn't actually contain any glue to connect the client to the x session, I use x11vnc as discussed in:
https://help.ubuntu.com/community/VNC/Servers

with a slight modification to the systemd ExecStart:
ExecStart=/usr/bin/x11vnc -auth guess -cursor_drag -forever -xkb -loop -repeat -rfbauth /home/username/.vnc/passwd -rfbport 5900 -shared

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]