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 #904035,
regarding tmux: segfault at 0 ip 00007f0d188b0d01 sp 00007fffe5bfb9c8 error 4 
in libc-2.27.so
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.)


-- 
904035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904035
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tmux
Version: 2.7-1+b1
Severity: normal

tmux just crashed for me, while editing a file in neovim. About 25 windows, 
only a single one visible, nothing remarkable done at that time.

I hope that it's not reproducible; loosing all the open editors hurts quite 
a bit ;/


The other bug reports have different IPs or are for 2.6, so I'm filing 
a new bug.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de (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 ---

Reply via email to