Your message dated Thu, 18 Oct 2018 22:16:48 +0200
with message-id <87r2gnrowf.fsf@silenus>
and subject line Closing with 2.8-1 upload
has caused the Debian Bug report #900505,
regarding segfault at 21c1, error 4 in tmux[559568e28000+84000]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
900505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900505
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tmux
Version: 2.7-1+b1
Severity: normal
Dear Maintainer,
I got this error:
tmux: server[2747]: segfault at 21c1 ip 0000559568e52a5a sp 00007ffefc121c68
error 4 in tmux[559568e28000+84000]
I'm not entirely sure how to reproduce it, I am filing this report in
case anyone else has the same issue. I'll add more information if I
manage to reproduce it.
I was using tmux with several panes and with fish shell, I had just copied
something to one of the panels and tmux crashed.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tmux depends on:
ii libc6 2.27-3
ii libevent-2.1-6 2.1.8-stable-4
ii libtinfo6 6.1+20180210-4
ii libutempter0 1.1.6-3
tmux recommends no packages.
tmux suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.8-1
I'm closing these crash bug reports opened against 2.7, 2.8 includes
many fixes for similar bugs so I'm just going to assume that these were
among them.
If you still get crashes in similar circumstances with 2.8-1, please
reopen. Thanks.
--- End Message ---
