Control: tags -1 - moreinfo On 2020-04-27 11:35:30 +0200, Axel Beckert wrote: > Vincent Lefevre wrote: > > After increasing the window width, I got an error > > A few question on the conditions under which this happened: > > * Do you happen to know from approximately which size to which size you > resized the window?
The initial width was 80 columns (as usual), and I increased it to about 90 columns. Note that the increase happens in real time, so that (almost?) each intermediate width was sent to Screen. > * In which terminal emulator did this happen? xterm > * What applications were running inside the screen session when it > crashed. Any TUI fullscreen programs like htop, ncdu, mutt, mc, vim, > emacs, etc.? In the current screen, it was Mutt in Attachment menu. The width was too small to see some entries entirely; that's the reason why I increased the width. There were normally 2 screens in the session, the other one running zsh and a Mutt started from zsh. > > Error: Cannot find master process to attach to! > > Press [Enter] to quit. > > > > Then the screen session was lost. > > I assume the resizing and this dialog happened while the session was > attached to the resized terminal. Yes. Note also: no core dumps, nothing interesting in the journalctl logs. I've tried to reproduce the issue under similar conditions, e.g. with various resizes while and after viewing attachments, but I couldn't. Currently I'm wondering whether a race condition with signals, such as SIGWINCH, could be the cause. This could explain why this is not reproducible. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
