Fedora Account System
Red Hat Associate
Red Hat Customer
If I start xrdp on a server I get a connection log that finishing ... started connecting connecting to 127.0.0.1 5910 error - problem connecting however if I click ok and try again the connection works. It seems like the desktop processes are starting but xrdp was trying to connect too early before the processes are ready to receive it, but it does connect to these processes on the second attempt. I suspect the solution is for xrdp to wait a bit longer before trying to connect to the processes it is starting (this is with the gnome windows manager).
Confirmed, with an out-of-the-box installation of xrdp-0.5.0-0.6.20090811cvs.fc12.i686 (I was _sure_ it was because /etc/xrdp/sesman.ini references a tsusers group which wasn't created, but apparently that group isn't used at all ...)
(In reply to comment #1) > Confirmed, with an out-of-the-box installation of > xrdp-0.5.0-0.6.20090811cvs.fc12.i686 > > (I was _sure_ it was because /etc/xrdp/sesman.ini references a tsusers group > which wasn't created, but apparently that group isn't used at all ...) if the group exist`s only users in the group are allowed to login. this is not the problem, this bug will be fixed in the next version.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This looks to be working again in Fedora 14.
(In reply to comment #4) > This looks to be working again in Fedora 14. I disagree; I saw it yesterday when I used xrdp for the first time on a f14 machine. See also http://sourceforge.net/mailarchive/message.php?msg_name=AANLkTi%3D%2BHyWCFdD6DcyCy8VaGWgUh%2BNPVVkzr2JY78eg%40mail.gmail.com (http://goo.gl/su20n)
Okay, if others are still seeing the problem in Fedora 14 I will reopen the bug.
please try this version and give me a feedback http://koji.fedoraproject.org/koji/buildinfo?buildID=205355
I can also confirm that I see this problem on a newly installed F14 virtual machine running on vmware esx. xrdp-0.5.0-0.13.fc14.x86_64
I'm seeing what may be the same problem on F16. In my case, xrdp gets a little farther: ... started connecting connecting to 127.0.0.1 5930 tcp connected security level is 2 (1 = none, 2 = standard) password ok sending share flag receiving server init error - problem connecting ... and it hangs there. Nothing obvious in /var/log/xrdp-sesman.log: [20120223-10:24:46] [INFO ] ++ created session (access granted): username fche, ip 192.168.1.1:41384 - socket: 7 [20120223-10:24:46] [INFO ] starting Xvnc session... [20120223-10:24:46] [INFO ] starting xrdp-sessvc - xpid=22657 - wmpid=22656 [20120223-10:24:46] [INFO ] ++ terminated session: username fche, display :30.0, session_pid 22655, ip 192.168.1.1:41384 - socket: 7 Starting Xvnc by hand on that machine works.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'm seeing this problem into Fedora 17.
Apparently still an issue in Fedora 17. Reopening...
+1 I have the same problem in Fedora 17: xrdp-0.6.0-0.5.fc17.x86_64 First login fails, but second login is success.
I had the same problem in Fedora 16 and still have it after upgrading to fedora 17:xrdp-0.6.0-0.5.fc17.x86_64 At work we have A RedHat el5 and el6 using xrdp 0.5.0-0.2 and 0.5.0-0.13 that do not have the issue of failing the first time to login when connecting from Windows 7.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.