Bug 424169

Summary:	Upgrading to =app-misc/screen-4.0.3-r5 makes current screen sessions inaccessible
Product:	Gentoo Linux	Reporter:	Joe Kappus <joe>
Component:	Current packages	Assignee:	Sven Wegener <swegener>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kripton, shell-tools, xmw
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	423775

Description Joe Kappus 2012-06-29 21:27:02 UTC

Upgrading screen to r5 makes reattaching sessions from r4 impossible.

Reproducible: Always

Steps to Reproduce:
1. Upgrade to =app-misc/screen-4.0.3-r5 from =app-misc/screen-4.0.3-r4
2. Try to reattach to running screen session with screen -r
Actual Results:  
screen -r output:

There is no screen to be resumed.

screen -list output: 

No Sockets found in /home/user/.screen.

Expected Results:  
Reattach to running screen session. Processes continue to run in the old screen session but remain inaccessible until downgrading to =app-misc/screen-4.0.3-r4.

Please mark this as blocking #423775.  

r4 did not store screen sockets in $HOMEDIR/.screen/, r5 does now?

Comment 1 Michael Weber (RETIRED) gentoo-dev

2012-06-29 23:04:36 UTC

from /usr/portage/app-misc/screen/ChangeLog

*screen-4.0.3-r5 (24 May 2012)

  24 May 2012; Jeremy Olexa <darkside@gentoo.org> +screen-4.0.3-r5.ebuild:
  Revision bump to disable socket dir (and use ~/.screen/ instead) for cases
  where /var/run is tmpfs, etc. This seems more portable and has been the best
  solution proposed on bug 333821

Workaround

mkdir ~/.screen
ln -s /var/run/screen/S-$(whoami)/* ~/.screen/

Comment 2 Michael Weber (RETIRED) gentoo-dev

2012-06-29 23:09:00 UTC

USE=multiuser emerge -av1 app-misc/screen

but this __is__ annoying.

An elog might have been appropriate.

Comment 3 jannis 2012-07-01 13:52:53 UTC

Yep, elog would've been nice ...

Comment 4 Eugeny Shkrigunov 2012-07-02 12:34:43 UTC

Hi!
Sorry for my English.

In 4.0.3-r5 regardless of USE-flag "multiuser":
  is no keepdir for /var/run/screen
  /var/run/screen does not have the correct access rights, that were established in pkg_postinst section 4.0.3-r4.ebuild
Error: Directory '/var/run/screen' must have mode 755.

The new defaults (--disable-socket-dir) are inconvenient: you can not do
  sudo bash
  screen
Error: You are not the owner of /home/username/.screen

Comment 5 Jeremy Olexa (darkside) (RETIRED) archtester

2012-07-02 13:35:59 UTC

There is no good solution, sorry for the trouble(s) - you will have to adapt.

*** This bug has been marked as a duplicate of bug 333821 ***