*** This bug is a duplicate of bug 330322 ***
https://bugs.launchpad.net/bugs/330322
Please disregard my suggestions, they were incorrect and off base.
I have uploaded a fix. Please test byobu 2.7, or the screen-profiles
version in jaunty-proposed.
:-Dustin
--
screen -d -m is broken due t
*** This bug is a duplicate of bug 330322 ***
https://bugs.launchpad.net/bugs/330322
???
I already have had a .screenrc file for a long time, and selecting a
profile is fine when running screen in a terminal, but neither one of
these suggestions helps my init scripts work during bootup.
--
*** This bug is a duplicate of bug 330322 ***
https://bugs.launchpad.net/bugs/330322
** This bug has been marked a duplicate of bug 330322
please don't bother me with a prompt about profiles
--
screen -d -m is broken due to it asking for profile
https://bugs.launchpad.net/bugs/378270
You
As a work-around, you can either touch ~/.screenrc, or run select-
screen-profile. I'm looking for an acceptable way to fix this for
Jaunty. As I have said before, this is fixed in Karmic.
:-Dustin
--
screen -d -m is broken due to it asking for profile
https://bugs.launchpad.net/bugs/378270
Yo
I would also like to request this get fixed in Jaunty. This is a big
pain in the butt for me becuase I have init scripts that run screen and
then other init scripts that run AFTER the ones which call screen and
are depending on that screen program to be running! I don't understand
why I can star
Hello,
Thanks for the bug report.
Okay, let me explain the changes I made to this bug...
First, this is not a bug against screen, but against a new package in
jaunty called screen-profiles (which has been renamed to byobu).
The issue as you describe it is a real one in Jaunty, but it has been
f
