Thanks for checking Gustavo. Since you mentioned this is not
reproducible in Ubuntu 20.04 I'll be marking this bug as Invalid.
** Changed in: screen (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
Hi,
I can confirm that this does not happen in plain Ubuntu Desktop 20.04. I
winder why in KDE Neon 20.04 does happens since is based in Ubuntu
20.04... I will have to report to them.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, today I have some time, I am installing Ubuntu Desktop 20.04 in
VirtualBox.
Meanwhile, the only way to keep a session alive (in KDE Neon 20.04) is
by using:
systemd-run --scope --user screen
Will keep posted once I've tested in the Ubuntu installation.
--
You received this bug
Hi Gustavo,
Thanks. Let us know when you've found sometime to do that. No rush,
absolutely. Meanwhile I am working this bug as "Incomplete". Please set
it back to "New" once you've reported your findings. Thanks!
** Changed in: screen (Ubuntu)
Status: New => Incomplete
** Changed in:
Hi,
I did not forgot this, but I reallt didn' t have time to test in a VM.
But, I've installed a new machine with same OS (KDE Neon 20.04) and the
same thing happens.
So, like I said before, this does not happen don upgraded machine from
18.04 to 20.04.
I will try to test in VM with Gnome
Hi,
Sure, I will let you know here the results. Also, I will try to modify
login.conf as suggested in the link before doing any test. But anyways,
is this was not affected in my other upgrades installations, I don't
think that is the problem here, but won't hurt me trying.
--
You received this
Since this started to seem different between Mate as discussed above I was
giving a few more terminals I regularly use a try:
- tilix (VTE based) - warns me that I'll close processes under this session,
keeps screen alive detached
- yakuake (kde based) - warns me that I'll close processes under
Well, is a really close (or same) behaviur like exposed in
https://bugs.debian.org/825394 (shared by Axel).
Screen version 4.8.0-1. The system (or either systemd) has modifications
at all, so is really weird.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi, first of all I don' t know why I did' t receive any notification of
this bug report.
Second, and to clarify, I being using screen command since 2000 (which
Is my beginning as Linux admin). This being said, I know how it works.
All my other Ubuntu upgrades from 18.04 to 20.04, this does not
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
Thanks Axel,
I think I didn't closed a terminal windows with anything other but CTRL+D for
years (which is an implicit call to exit), but you are absolutely right. It
could be "click on the X on the window decoration to close the terminal".
Thanks for making me see that ... :-)
@Gustavo - never
@paelzer: This does not sound like exiting the last shell inside the
screen session but closing the xterm/gnome-terminal/lxterminal etc. it
is running in. (Back to "New" for that.)
So in the end this sounds a lot like one of these annoying systemd bugs,
e.g. similar to
If I "exit" from a screen I'd always expect it is gone.
You'd usually only detach to leave it around like "CTRL+A D" and then you can
later reattach.
So you are saying you formerly could
ssh to target and then:
$ screen
# enters the screen session
$
$ exit
# left the screen
$ screen -x
#
** Project changed: launchpad => screen (Ubuntu)
** Description changed:
In a new fresh installed 20.04, when I use screen command and close the
- terminal (not closing screen sesion), then I can recover it with screen
- -x, since does not exist. I can only recover screen sesion if the
+
14 matches
Mail list logo
