That's interesting, I just performed your suggested test, and I couldn't reproduce - it's a fresh Ubuntu 20.04 install, running MATE (not KDE!) and GNU screen 4.8.0-1. After closing the terminal, I've opened another one and "screen -x" worked fine, as expected.
Could you try to use MATE / Gnome to perform your test? So we can isolate it to KDE (or not). Also, which version of screen is installed in your system? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1900008 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1900008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
