Bug 2339004 - login via xrdp does not update utmp/btmp/lastlog
Summary: login via xrdp does not update utmp/btmp/lastlog
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: xrdp
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bojan Smojver
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-20 14:46 UTC by Magnus Lewis-Smith
Modified: 2025-02-15 03:09 UTC (History)
2 users (show)

Fixed In Version: xrdp-0.10.2-9.fc40 xrdp-0.10.2-9.fc41 xrdp-0.10.2-9.el8 xrdp-0.10.2-9.el9
Clone Of:
Environment:
Last Closed: 2025-02-15 02:22:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Patch to support upstream PR 3400 (27.26 KB, patch)
2025-01-27 13:29 UTC, Magnus Lewis-Smith
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Github neutrinolabs xrdp pull 3400 0 None open Add utmp/wtmp support (v0.10) 2025-01-20 20:09:32 UTC

Description Magnus Lewis-Smith 2025-01-20 14:46:56 UTC
Description of problem:
Remote login via xrdp does not update utmp

Version-Release number of selected component (if applicable):
xrdp-1:0.10.2-7.el9

How reproducible:


Steps to Reproduce:
1. user login to system via rdp
2. 'who' / 'w'

Actual results:
(no output)

Expected results:
'who' / 'w' output describing current user login

Additional info:
Known bug, fixed upstream in devel branch but not yet backported into stable 0.10 branch
- https://github.com/neutrinolabs/xrdp/pull/2745
- https://github.com/neutrinolabs/xrdp/discussions/2744

Comment 1 Magnus Lewis-Smith 2025-01-20 14:49:42 UTC
A pull request is pending to port the fix into the 0.10 stable branch.  

If accepted, would you consider applying it to the 0.10.2 release, or prefer to wait for the next stable 0.10.3 release?

Comment 2 Bojan Smojver 2025-01-20 20:10:04 UTC
Happy to patch once it gets merged upstream.

Comment 3 Magnus Lewis-Smith 2025-01-27 13:29:12 UTC
Created attachment 2074003 [details]
Patch to support upstream PR 3400

xrdp pull request 3400 accepted upstream

The attached patch 
- backports the changes on v0.10 branch into v0.10.2 (xrdp-0.10.2-utmpfix.patch)
- updates specfile with necessary build flag '--enable-utmp'
- updates 'xrdp-sesman.pamd' with necessary pam modules

Comment 4 Bojan Smojver 2025-01-28 23:09:20 UTC
Thanks for the patch. Just out of curiosity, does loginctl not tell you who's logged in via xrdp?

Comment 5 Magnus Lewis-Smith 2025-01-29 14:32:28 UTC
(In reply to Bojan Smojver from comment #4)
> ... Just out of curiosity, does loginctl not tell you
> who's logged in via xrdp?

yes, it does, and arguably contains more useful information.  Nevertheless, for completeness and a more "unix-y" way :)

Comment 6 Fedora Update System 2025-02-06 01:40:03 UTC
FEDORA-2025-a1e945877a (xrdp-0.10.2-9.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a1e945877a

Comment 7 Fedora Update System 2025-02-06 01:40:04 UTC
FEDORA-EPEL-2025-6b6779ae97 (xrdp-0.10.2-9.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-6b6779ae97

Comment 8 Fedora Update System 2025-02-06 01:40:05 UTC
FEDORA-EPEL-2025-cad1dbad78 (xrdp-0.10.2-9.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-cad1dbad78

Comment 9 Fedora Update System 2025-02-07 01:30:19 UTC
FEDORA-2025-0748bff73e has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-0748bff73e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0748bff73e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2025-02-07 01:58:32 UTC
FEDORA-EPEL-2025-cad1dbad78 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-cad1dbad78

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2025-02-07 02:22:13 UTC
FEDORA-EPEL-2025-6b6779ae97 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-6b6779ae97

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2025-02-07 02:43:39 UTC
FEDORA-2025-a1e945877a has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-a1e945877a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a1e945877a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2025-02-15 02:22:14 UTC
FEDORA-2025-a1e945877a (xrdp-0.10.2-9.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2025-02-15 02:35:42 UTC
FEDORA-2025-0748bff73e (xrdp-0.10.2-9.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-02-15 02:56:48 UTC
FEDORA-EPEL-2025-6b6779ae97 (xrdp-0.10.2-9.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2025-02-15 03:09:04 UTC
FEDORA-EPEL-2025-cad1dbad78 (xrdp-0.10.2-9.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.