I've been able to reproduce this bug, also on a shared server providing shells for a lot of users.
It looks like an agressive setup regarding user limits: attached is the output of `ulimit -a' on such a server.
Particulary interesting is the 'max user processes' which is set to 24; since byobu is written in bash, it means a lot of forks (and I guess each status notification runs in a separate process).
I've been able to reproduce this bug, also on a shared server providing shells for a lot of users.
It looks like an agressive setup regarding user limits: attached is the output of `ulimit -a' on such a server.
Particulary interesting is the 'max user processes' which is set to 24; since byobu is written in bash, it means a lot of forks (and I guess each status notification runs in a separate process).