xrdp login failed

English Network/Internet
1

Hi,
I got xrdp installed on OpenSUSE11.0/GNOME 2.22. I remote desktopped to the OpenSUSE box from my windows box (Remote Desktop COnnection) and everything was working gloriously for about 45 minutes.

I had to do a make, so I went out to lunch. When I got back the remote desktop session to my OpenSUSE box was still up, I could move windows around, but it wasn’t accepting any keyboard input. So I rebooted the OpenSUSE machine, started XRDP again, and remote desktopped in again from the windows box. I get the login user name / password / session dialog box. When I entered those parameters in (session = GNOME) I get:
connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to sesman
login failed

Checking the log (var/log/xrdp-sesman.log)
granted TS access to user user
startign Xdmx session…
error X server died - user user - pid 9222
Any ideas?

It was really cool when it was working…

Thanks!
Scott

2

I have the same issue -
is there a fix available ?

3

I got it working, and I’m using kde

edit /ect/pam.d/xrdp-sesman
change it to

#%PAM-1.0
auth required pam_unix.so shadow nullok
account required pam_unix.so

4

So, this solution didn’t help me

5

I’m sorry I responded to the wrong post

6

Hi,

the suggestion was to change /etc/pam.d/xrdp-sesman file, but in my system (openSUSE11.1 i586), this file has exactly that content by default.

I’ve managed to overcome sesman login failed error by copying /etc/pam.d/xrdp-sesman to /etc/pam.d/sesman
I.e. /etc/pam.d/sesman file was missing.

But know I have another error about screen depth. Does anyone can give a suggestion to solve this?

========
connecting to sesman ip 127.0.0.1 port 3500
sesman connect ok
sending login info to sesman
login successful for display 10
started connecting
rdpx11 channel is not present
X11 RDP server started
Screen depth is not 24

Regards,
Mindaugas

7

BTW, if I tru rdp to connect from vnc session (rdesktop localhost), I get:

=============
connecting to sesman ip 127.0.0.1 port 3500
sesman connect ok
sending login info to sesman
login successful for display 10
started connecting
rdpx11 channel is present
rdpx11 connection initiated
error - screen doesn’t support visual: class: truecolor, depth: 32 planes, available

Regards,
Mindaugas

8

Hi,

SOLVED :slight_smile:

Just press “Options >>” -> Display -> Colors -> True color (24bit) in Windows remote desktop client. I can connect know.

Regards,
Mindaugas

9

Hi,

after a few successful logins I have again:

connecting to sesman ip 127.0.0.1 port 3500
sesman connect ok
sending login info to sesman
login failed

No, configuration was changed no xrdp service restart was done. Restarting does not help. Don’t have any ideas…

Regards,
Mindaugas

10

Same issue here.

The only difference is i use rdesktop on Solaris to connect to my notebook at home from work


 ./rdesktop -u whatverusername -f -g 1024x786 -B -a 16 -z -r clipboard:PRIMARYCLIPBOARD -r sound:remote 1.1.1.1

Configentries


HP-Brett:/etc/pam.d # cat xrdp-sesman
#%PAM-1.0
auth       include      common-auth
account    include      common-account

I also have recognized that after a unsuccesful login (which is normal at the moment) the sesman process gets killed.
Unfortunately the pid has to be erased manually


HP-Brett:/etc/pam.d # ps -ef|grep xrd
root     30358     1  8 07:00 pts/5    00:00:49 /usr/sbin/xrdp
root     30397 28202  0 07:10 pts/5    00:00:00 grep xrd

HP-Brett:/etc/pam.d # /usr/sbin/xrdp-sesman
starting sesman...
sesman is already running.
if it's not running, try removing /var/run/sesman.pid
HP-Brett:/etc/pam.d #

The sesman starts up after removing the pid
but dies at login.

Versions used.
xrdp: A Remote Desktop Protocol server.
Copyright (C) Jay Sorg 2004-2008
See xrdp homepage for more information.
Version 0.5.0


/varlog/xrdp-sesman.log
20090131-05:27:52] [INFO ] listening...
[20090131-05:28:57] [WARN ] [init:45] libscp initialized
[20090131-05:28:58] [CORE ] starting sesman with pid 15131
[20090131-05:28:58] [INFO ] listening...
[20090131-05:36:11] [WARN ] [init:45] libscp initialized
[20090131-05:36:11] [CORE ] starting sesman with pid 15272
[20090131-05:36:11] [INFO ] listening...
[20090131-07:03:44] [WARN ] [init:45] libscp initialized
[20090131-07:03:44] [CORE ] starting sesman with pid 18172
[20090131-07:03:44] [INFO ] listening...
[20090201-06:56:49] [WARN ] [init:45] libscp initialized
[20090201-06:56:49] [CORE ] starting sesman with pid 30295
[20090201-06:56:49] [INFO ] listening...
[20090201-07:01:21] [WARN ] [init:45] libscp initialized
[20090201-07:01:21] [CORE ] starting sesman with pid 30363
[20090201-07:01:21] [INFO ] listening...
[20090201-07:13:20] [WARN ] [init:45] libscp initialized
[20090201-07:13:21] [CORE ] starting sesman with pid 30406
[20090201-07:13:21] [INFO ] listening...
[20090201-07:13:20] [WARN ] [init:45] libscp initialized
[20090201-07:13:21] [CORE ] starting sesman with pid 30406
[20090201-07:13:21] [INFO ] listening...
Segmentation fault

Not a real useful output.
Only the message about the segmentation fault.
I tried the stable package and the Factory Packaged but there’s no change in behaviour.

11

Hi.

I have the same problem. Is it possible to change the color depth at the server to 16 bit and not at the client to 24 bit.

xrdp-sesrun could work with the bpp as parameter, but I don’t know where put the parameter. Maybe in an ini file like sesman.ini

12

dentzer,

Did you find a way to change the configuration on the server to allow client connections with a color depth of 16 bit instead of 24 bit?

I am trying to connect over a lower bandwidth connection and I do not want to have to be forced to connect at 24 bit color depth from the client machine.

thanks

13

See Nomad - openSUSE for instructions on how to apply updates to xrdp on OpenSuse 11.1

14

I’ve just tried this and am having the same connection issue:

sending login info to sesman
login failed

but executing the link

cp /etc/pam.d/xrdp-sesman /etc/pam.d/gdm

does not change things.

I can successfully login using failsafe terminal, but get no love from KDE.

15

UPDATE:

I can successfully login using failsafe terminal, but get no love from KDE3, KDE4, IceWM, or TWM. …so it might not be just a KDE issue?

I also tried following the advice from a Novell posting on the issue with no success. It doesn’t seem to matter whether the first user to attempt remote access is root.

16

Agree with CWDillon, I can confirm sucsessuful instalation of XRDP on opensuse 11.2 using the nomad repository for opensuse 11.1 , so open 11.2 evrything works great, but in 11.1 i was able to login only into the failsave mode.

here is what i see:

connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to sesman
login successful for display 10
started connecting
rdpx11 channel is not present

//I found the following in my messages log:

Jan 15 00:38:28 linux-a9id xrdp-sesman: pam_warn(xrdp-sesman:session): function=[pam_sm_open_session] service=[xrdp-sesman] terminal=:11] user=[tito] ruser=<unknown>] rhost=<unknown>]
Jan 15 00:38:41 linux-a9id xrdp-sesman: pam_warn(xrdp-sesman:session): function=[pam_sm_open_session] service=[xrdp-sesman] terminal=:11] user=[tito] ruser=<unknown>] rhost=<unknown>]

clients-pools:~ # uname -a
Linux clients-pools 2.6.27.39-0.2-xen #1 SMP 2009-11-23 12:57:38 +0100 x86_64 x86_64 x86_64 GNU/Linux

all pakages are installed from the opensuse 11.1 normad repository!

17

I’m sorry about my english,
I added my user to tsusers group looking to [security] in /etc/xrdp/sesman.ini

[Security]
AllowRootLogin=1
MaxLoginRetry=4
TerminalServerUsers=tsusers
TerminalServerAdmins=tsadmins

After a reboot (oops!!) I could connect me Ok!

18

========
connecting to sesman ip 127.0.0.1 port 3500
sesman connect ok
sending login info to sesman
login successful for display 10
started connecting
rdpx11 channel is not present
X11 RDP server started
Screen depth is not 24

Hi

Go to the options tab in remote desktop connections and click on display tab and make ur depth as 24 bit true color in the pc which u are using to connect linux PC