http://bugzilla.opensuse.org/show_bug.cgi?id=1203468 http://bugzilla.opensuse.org/show_bug.cgi?id=1203468#c1 Joe S changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |sndirsch@suse.com --- Comment #1 from Joe S --- Is anyone looking at this bug? It's been 1 and a half months and it seems like my report shows what change broke it From the bug report it seems pretty clear that the changes made between xrdp-0.9.19-1.1.x86_64.rpm ( which is in 20220813 ) and xrdp-0.9.19-1.2.x86_64.rpm ( which is in 20220908 ) is the source of the problem since reverting back to xrdp-0.9.19-1.1.x86_64.rpm resolves the issue and xrdp works fine with the prior version. Today I updated one of my machines to TW 20221024 which is still using the broken xrdp-0.9.19-1.2.x86_64.rpm version and as expected xrdp is still broken. Installing the prior verion which I had saved ( xrdp-0.9.19-1.1.x86_64.rpm ) once again provides a working xrdp environment. Do you need more details or do we need to add someone else to the bug report to look at the issue? Thank you for your time! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1203468 Hans-Peter Jansen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hpj@urpla.net -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1203468 http://bugzilla.opensuse.org/show_bug.cgi?id=1203468#c9 --- Comment #9 from Joe S --- (In reply to Dominique Leuenberger from comment #7)

(In reply to Yifan Jiang from comment #5)

...

I am not sure how to revert to a precedent binary package since when there was no source update. But probably we need to do that if it is a general issue.

@Dominique, do you think there is a way to do it technically? Thanks!

That's not possible - we need to find out whats the difference between the two builds that resulted in this issue

I am sure there are parts to the process that I don't understand but I am surprised at your answer as I have seen different versions of a package available within a build before. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1203468 http://bugzilla.opensuse.org/show_bug.cgi?id=1203468#c25 Joe S changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #25 from Joe S --- (In reply to Stefan Dirsch from comment #24)

This is already fixed in Tumbleweed.

------------------------------------------------------------------- Mon Nov 7 10:48:57 UTC 2022 - Daike Yu

- Add xrdp-update-pam.d-path.patch (bsc#1203468) + Update pam.d path in install scripts to allow correct rule guess.

Hi Stefan, Sorry to report that it is still not fixed. Today I updated from 20221101 to TW 20221202 and xrdp is still broken. After updating to TW 20221202, I Removed xrdp and xorgxrdp packages Removed my /etc/pam.d/xrdp-sesman Which was renamed to xrdp-sesman.rpmsave by the package removal Rebooted Installed xrdp and xorgxrdp packages Started and enabled the xrdp service Verified firewall had port open for zone Here is the xrdp.sesman file that was installed from 20221202 #%PAM-1.0 # # Really basic authentication set when nothing else is available # # You may need to edit this to suit your system depending on the # required functionality. # auth required pam_unix.so shadow auth required pam_env.so password required pam_unix.so account required pam_unix.so account required pam_nologin.so session required pam_unix.so Tried remote desktop to machine and get the SAME errors as initially reported ( here the are again ) The Connection Log is not real useful: Connecting to sesman on 127:0.0.1:3350 sesman connect ok sending login info to session manager.Please wait.. login successful for user denise on display 200 VNC started connecting Waiting 2000 ms for VNC to start... VNC connecting to 127.0.0.1.6100 VNC error - problem connecting some problem Error connecting to user session To resolve I did the following: Edit /etc/pam.d/xrdp-sessman and add session include common-session systemctl daemon-reload systemctl restart xrdp xrdp now working again. Seems that the fix is to add the line to xrdp-sesman which I included which wold resolve the issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1203468 http://bugzilla.opensuse.org/show_bug.cgi?id=1203468#c27 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS --- Comment #27 from Stefan Dirsch --- Hmm. Seems the patch is only applied on SLE, but not on Tumbleweed. No idea why. [...] Patch15: xrdp-update-pam.d-path.patch [...] %prep %setup -q %patch1 -p1 %patch4 -p1 %patch5 -p1 %patch6 -p1 %if 0%{?sle_version} %patch11 -p1 %patch12 -p1 %patch13 -p1 %patch14 -p1 %patch15 -p1 %endif [...] -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1203468 http://bugzilla.opensuse.org/show_bug.cgi?id=1203468#c29 --- Comment #29 from Daike Yu --- Fix submitted to X11:RemoteDesktop. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1203468 http://bugzilla.opensuse.org/show_bug.cgi?id=1203468#c31 --- Comment #31 from Joe S --- I just update from TW 20221202 to 20221205 which includes the patch. It properly created the /etc/pam.d/xrdp-sesman.rpmnew file. I replaced /etc/pam.d/xrdp-sesman with the rpmnew file, restarted the service and as expected everything is working. Thanks to all for your help in resolving this. -- You are receiving this mail because: You are on the CC list for the bug.