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 start the scripts manually and don't have this problem. Can the startup order of something be modified to inform screen that a profile was already selected, as a workaround?
-- screen -d -m is broken due to it asking for profile https://bugs.launchpad.net/bugs/378270 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
