First, could you try the latest 3.x byobu tarball from https://launchpad.net/byobu/+download? These use "./configure --prefix=/path/to/wherever && make && make install" style installation, and have subsequently deprecated byobu-export.
Secondly (and more to the point of your bug), where is your SSH_AUTH_SOCK located?
The "setenv SSH_AUTH_SOCK /var/run/screen/S-$USER/byobu.ssh-agent" points SSH_AUTH_SOCK to a symlink that byobu tries to maintain against the real socket. You can certainly comment that line out, but it will be up to you (and your shell profile, etc) to maintain the accuracy of that socket across multiple attaches/detaches. That's the reason for the link. It allows Byobu to always look for that socket at the same path, which is a link that can be trivially updated.
I suspect (?) that your problem is that /var/run/screen/* doesn't exist for you on this system where byobu isn't actually installed from the package?
Hi Randy, thanks for the report.
First, could you try the latest 3.x byobu tarball from https:/ /launchpad. net/byobu/ +download? These use "./configure --prefix= /path/to/ wherever && make && make install" style installation, and have subsequently deprecated byobu-export.
Secondly (and more to the point of your bug), where is your SSH_AUTH_SOCK located?
The "setenv SSH_AUTH_SOCK /var/run/ screen/ S-$USER/ byobu.ssh- agent" points SSH_AUTH_SOCK to a symlink that byobu tries to maintain against the real socket. You can certainly comment that line out, but it will be up to you (and your shell profile, etc) to maintain the accuracy of that socket across multiple attaches/detaches. That's the reason for the link. It allows Byobu to always look for that socket at the same path, which is a link that can be trivially updated.
I suspect (?) that your problem is that /var/run/screen/* doesn't exist for you on this system where byobu isn't actually installed from the package?