screen-4.0.3_3+darwin_9 Screen breaks OSX CLI tools.

[lhunath@…]

When I upgraded from 4.0.3_1 to 4.0.3_3+darwin_9, certain OS X tools suddenly stopped working.

Examples are: pbcopy, pbpaste: Completely dead, no error messages, exit code 1. hdiutil attach: Doesn't contact the OS X keychain anymore for encrypted images.

Moreover, I noticed that 4.0.3_1 understood the deflogin and login screen commands (they are in my .screenrc) while 4.0.3_3 now complains about those. Also, my environment (set by .profile) is not kept when opening screens inside screen; so commands in .bashrc that depend on it, like PATH being set, started failing. I've had to add shell "-bash" to .screenrc to fix that, because it doesn't understand deflogin anymore.

For now; I'm staying on 4.0.3_1 until these issues are fixed.

Screen should understand deflogin and login, they are included in man screen.

[lhunath@…]

Cc Me!

[alakazam@…]

I have reproduced this bug ; it also occurs with the mate command line tool from TextMate.

The following blog posts are relevant to this issue, and the comments expand on the problem :

•  http://northstarlabs.net/2007/11/textmate-on-leopard-command-line-tool-fix/
•  http://blog.macromates.com/2007/leopard-issues/

[cpettitt@…]

Cc Me!

[cpettitt@…]

pbcopy and pbpaste are also broken since this change:  http://trac.macports.org/changeset/45746 (4.0.3_2).

I'm reverting back to 4.0.3_1 for now as well.

[raimue@…]

By applying Apple's patches we got to the same state as the system screen, which is broken in the same way. On the other hand, attach/detach was broken without these patches (#13732).

[rectalogic@…]

Apparently it is the call to _vprocmgr_move_subset_to_user in Apples patches (to migrate to a background session) that is the cause of all these issues.

 http://metastatic.org/text/Concern/tag/textmate/  http://lists.apple.com/archives/darwin-dev/2008/Jan/msg00218.html

[khalsah@…]

Cc Me!

[dan@…]

Cc Me!

[noah.easterly@…]

Cc Me!

[macports@…]

Cc Me!

[anonymous]

Milestone Port Bugs deleted

[lhunath@…]

Cc Me!

[jeremyhu@…]

Cc Me!

[macports@…]

Cc Me!

[joel.chippindale@…]

Cc Me!

[joel.chippindale@…]

Instructions for downgrading screen to @4.0.3_1  http://blog.monkeysthumb.org/2009/06/11/install-old-version-of-screen-using-mac-ports/

[gdelfino@…]

Cc Me!

[gdelfino@…]

Cc Me!

[gdelfino@…]

Cc Me!

[rtlechow@…]

Cc Me!

[macports@…]

Cc Me!

[macports@…]

Cc Me!

[toby@…]

There is no resolution for this ticket. Without that call, screen does not function in a very critical way - it doesn't persist if you log out. I'd consider that a much more important feature than being able to use pbcopy. Furthermore, this is fixed in SnowLeopard.

wontfix

[lhunath@…]

Does that mean that the patch that the situation is black or white? Either we apply the patch or we don't? The whole point for this ticket is to find a middle way; applying the functionality introduced by the patch while not breaking the existing functionality which involves any communication between the terminal and apple utilities (this is definitely not a case of just pbcopy being broken).

[jeremyhu@…]

The problem is with the behavior of launchd on Leopard. In essence, on Leopard, each login has its own separate launchd environment. On SL, it is per-user (thus you will share a launchd environment with your console login when you login via ssh or get a new login environment via screen). That is essentially the root of the problem here. If you're interested, Damien Sorresso gave a nice talk at WWDC this summer about the changes in SL's launchd. I believe either a webcast or slides may be available in Apple's dev-central...