Control: found -1 4.9.1-3.1
On 2025-10-05 12:52:39 +0200, Vincent Lefevre wrote:
> After resizing the terminal window where GNU Screen is running
> (with the Mutt MUA), I got:
>
> Error: Cannot find master process to attach to!
> Press [Enter] to quit.
I got a similar issue. I don't remember having resized the
terminal window, but a resize appears in the backtrace, which
is here different from my original bug report:
Core was generated by `/usr/bin/screen -c /home/vinc17/.screenrc-mutt -T
screen-256color-bce-s -dRR mutt -t mutt /home/vinc17/bin/smutt --'.
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (threadid=<optimized out>,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
⚠ warning: 44 ./nptl/pthread_kill.c: No such file or directory
(gdb) bt
#0 __pthread_kill_implementation (threadid=<optimized out>,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1 0x00007f5d0af7447f in __pthread_kill_internal (threadid=<optimized out>,
signo=6) at ./nptl/pthread_kill.c:89
#2 0x00007f5d0af1d942 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/posix/raise.c:26
#3 0x00007f5d0af054ac in __GI_abort () at ./stdlib/abort.c:77
#4 0x00007f5d0af064e5 in __libc_message_impl (
fmt=fmt@entry=0x7f5d0b08b34b "%s\n") at ../sysdeps/posix/libc_fatal.c:138
#5 0x00007f5d0af7e215 in malloc_printerr (str=<optimized out>)
at ./malloc/malloc.c:5895
#6 0x00007f5d0af7e231 in malloc_printerr_tail (str=<optimized out>)
at ./malloc/malloc.c:5912
#7 0x000055c999b506a8 in FreeMline (ml=ml@entry=0x55c99a9d8700)
at ../resize.c:431
#8 0x000055c999b52408 in ChangeWindowSize (p=0x55c99a73fce0,
wi=<optimized out>, he=<optimized out>, hi=<optimized out>)
at ../resize.c:885
#9 0x000055c999b58da9 in WinResize (wi=<optimized out>, he=<optimized out>)
at ../window.c:488
#10 0x000055c999b50fcd in ResizeLayer (l=<optimized out>, wi=80, he=59,
norefdisp=0x55c99a72cac0) at ../resize.c:390
#11 0x000055c999b69b55 in Activate (norefresh=norefresh@entry=0)
at ../process.c:5333
#12 0x000055c999b55969 in FinishAttach (m=m@entry=0x55c999baf0e0 <m>)
at ../socket.c:1578
#13 0x000055c999b5637d in ReceiveMsg () at ../socket.c:1249
#14 0x000055c999b8aa37 in sched () at ../sched.c:222
#15 0x000055c999b3de36 in main (ac=2, av=<optimized out>) at ../screen.c:1504
> In the journalctl output, there is something strange, but this might
> be unrelated:
[...]
Probably unrelated, as this time, there was nothing unusual in the
journalctl output.
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
