Verification: the failure is stochastic, so I am running the reproducer
three times per series

=== JAMMY ===

root@ephemeral-jammy-9979:~# apt-cache policy tmux
tmux:
  Installed: 3.2a-4ubuntu0.2
  Candidate: 3.2a-4ubuntu0.2
  Version table:
 *** 3.2a-4ubuntu0.2 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        100 /var/lib/dpkg/status
     3.2a-4build1 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@ephemeral-jammy-9979:~# sh repro.sh
server CRASHED after 1 rounds
root@ephemeral-jammy-9979:~# sh repro.sh
server CRASHED after 4 rounds
root@ephemeral-jammy-9979:~# sh repro.sh
server CRASHED after 4 rounds

on proposed:

root@ephemeral-jammy-9979:~# apt-cache policy tmux
tmux:
  Installed: 3.2a-4ubuntu0.3
  Candidate: 3.2a-4ubuntu0.3
  Version table:
 *** 3.2a-4ubuntu0.3 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     3.2a-4ubuntu0.2 500
        500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
     3.2a-4build1 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
root@ephemeral-jammy-9979:~# sh repro.sh
server survived 2000 rounds
root@ephemeral-jammy-9979:~# sh repro.sh
server survived 2000 rounds
root@ephemeral-jammy-9979:~# sh repro.sh
server survived 2000 rounds

=== NOBLE ===

root@ephemeral-noble-241:~# apt-cache policy tmux
tmux:
  Installed: 3.4-1ubuntu0.1
  Candidate: 3.4-1ubuntu0.1
  Version table:
 *** 3.4-1ubuntu0.1 500
        500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.4-1build1 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
root@ephemeral-noble-241:~# sh repro.sh
server CRASHED after 5 rounds
root@ephemeral-noble-241:~# sh repro.sh
server CRASHED after 5 rounds
root@ephemeral-noble-241:~# sh repro.sh
server CRASHED after 6 rounds

on proposed:

root@ephemeral-noble-241:~# apt-cache policy tmux
tmux:
  Installed: 3.4-1ubuntu0.2
  Candidate: 3.4-1ubuntu0.2
  Version table:
 *** 3.4-1ubuntu0.2 100
        100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     3.4-1ubuntu0.1 500
        500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
     3.4-1build1 500
        500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
root@ephemeral-noble-241:~# sh repro.sh
server survived 2000 rounds
root@ephemeral-noble-241:~# sh repro.sh
server survived 2000 rounds
root@ephemeral-noble-241:~# sh repro.sh
server survived 2000 rounds

=== RESOLUTE ===

root@ephemeral-resolute-413:~# apt-cache policy tmux
tmux:
  Installed: 3.6a-2ubuntu0.1
  Candidate: 3.6a-2ubuntu0.1
  Version table:
 *** 3.6a-2ubuntu0.1 500
        500 http://archive.ubuntu.com/ubuntu resolute-updates/main amd64 
Packages
        500 http://security.ubuntu.com/ubuntu resolute-security/main amd64 
Packages
        100 /var/lib/dpkg/status
     3.6a-2 500
        500 http://archive.ubuntu.com/ubuntu resolute/main amd64 Packages
root@ephemeral-resolute-413:~# sh repro.sh
server CRASHED after 20 rounds
root@ephemeral-resolute-413:~# sh repro.sh
server CRASHED after 1 rounds
root@ephemeral-resolute-413:~# sh repro.sh
server CRASHED after 47 rounds

on proposed:

root@ephemeral-resolute-413:~# apt-cache policy tmux
tmux:
  Installed: 3.6a-2ubuntu0.2
  Candidate: 3.6a-2ubuntu0.2
  Version table:
 *** 3.6a-2ubuntu0.2 100
        100 http://archive.ubuntu.com/ubuntu resolute-proposed/main amd64 
Packages
        100 /var/lib/dpkg/status
     3.6a-2ubuntu0.1 500
        500 http://archive.ubuntu.com/ubuntu resolute-updates/main amd64 
Packages
        500 http://security.ubuntu.com/ubuntu resolute-security/main amd64 
Packages
     3.6a-2 500
        500 http://archive.ubuntu.com/ubuntu resolute/main amd64 Packages
root@ephemeral-resolute-413:~# sh repro.sh
server survived 2000 rounds
root@ephemeral-resolute-413:~# sh repro.sh
server survived 2000 rounds
root@ephemeral-resolute-413:~# sh repro.sh
server survived 2000 rounds

Fixed everywhere. The test failure on jammy was an infra tmpfail, and
has been retried.

** Tags removed: verification-needed-jammy verification-needed-noble 
verification-needed-resolute
** Tags added: verification-done-jammy verification-done-noble 
verification-done-resolute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169164

Title:
  tmux server SIGSEGV in control_write() when a control-mode client is
  still connecting (fixed upstream in 3.7)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/2169164/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to