Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session disconnects, can't reconnect during Ubuntu system upgrade #2245

Closed
jpmorrison opened this issue May 1, 2022 · 3 comments
Closed

Comments

@jpmorrison
Copy link

Connected to Ubuntu 20.04 with MS RDP. Xrdp was installed from Ubuntu repositories

Ran do-release-upgrade -d in a terminal window and the RDP session dropped.
Reconnecting shows the log/login prompt - after logging in the session is dropped again.

Not sure which logs are useful
/var/log/auth,log

May  1 15:54:19 ubuntu-test xrdp-sesman[2269689]: pam_unix(xrdp-sesman:session): session opened for user jmorrison(uid=1000) by (uid=0)
May  1 15:54:19 ubuntu-test systemd-logind[4244]: New session c19 of user jmorrison.
May  1 15:54:20 ubuntu-test systemd-logind[4244]: Failed to restore VT, ignoring: Bad file descriptor
May  1 15:54:21 ubuntu-test xrdp-sesman[2269689]: pam_unix(xrdp-sesman:session): session closed for user jmorrison
May  1 15:54:21 ubuntu-test systemd-logind[4244]: Session c19 logged out. Waiting for processes to exit.
May  1 15:54:30 ubuntu-test systemd-logind[4244]: Removed session c19.
@bmullan
Copy link

bmullan commented May 1, 2022 via email

@matt335672
Copy link
Member

I think this is a consequence of two things:-

  1. sesman is not currently restartable (Running sessions "lost" if xrdp-sesman restarts #800). This is being worked on, but is a major change (see Redesign of authentication architecture #1961).
  2. Systems using systemd --user don't allow more than one graphical session per user. This isn't something we can work around in xrdp, but it might be possible by using containerised desktops.

When xrdp is upgraded, it will need to be stopped and restarted. This leaves an orphaned session (point 1). Because this session is active according to systemd however, you will be unable to start a new one (point 2).

I can understand you really want to connect to the old session however, to see how things have gone. Have you got another machine running with a graphical login available?

@matt335672
Copy link
Member

No response from OP - closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants