screen multiplexer and xvesa

[alu]

i have compiled screen and make both tce/tcz extensions; no problem so far, but i was not happy with my test and could not find help out of google, so i would like to know your minds on this:

i am running mc2.3 with the standard xvesa-core extension; screen (tcz in this case) loads nicely; i run it as tc user in aterm and can use it without issue; but when i ctrl+alt+bckspce to terminal and want to run screen from terminal, i have to run it with root privileges (i don't want it) in order to open a session; and when i run it with root privileges (sudo screen), screens hangs after seconds...

why does screen behave that way in terminal?

[mikshaw]

Screen needs to be able to write to the terminal device.
I haven't used it in TC, but I recall I needed to give the regular user ownership of /dev/tty1 (or whatever tty is desired) in order to use screen in DSL.  I think the issue lies in how the user is logged in...the user is su'd from root rather than given a login, so the tty is still owned by root.
sudo chown 1001 /dev/tty1

[jpeters]

i have compiled screen and make both tce/tcz extensions; no problem so far, but i was not happy with my test and could not find help out of google, so i would like to know your minds on this:

i am running mc2.3 with the standard xvesa-core extension; screen (tcz in this case) loads nicely; i run it as tc user in aterm and can use it without issue; but when i ctrl+alt+bckspce to terminal and want to run screen from terminal, i have to run it with root privileges (i don't want it) in order to open a session; and when i run it with root privileges (sudo screen), screens hangs after seconds...

why does screen behave that way in terminal?

I use screen-4.9.2, and don't have that problem using tc_2.3 (haven't tried with mc). 

[jpeters]

Screen needs to be able to write to the terminal device.
I haven't used it in TC, but I recall I needed to give the regular user ownership of /dev/tty1 (or whatever tty is desired) in order to use screen in DSL.  I think the issue lies in how the user is logged in...the user is su'd from root rather than given a login, so the tty is still owned by root.
sudo chown 1001 /dev/tty1

I don't know much about terminal devices, but tty0, tty1, and tty2 are tc:staff, and the rest
are root:staff on my setup (logged in as tc). 

[mikshaw]

Maybe alu's not having the same issue that I had, then.  But it still sounds like a permissions problem.  Are you using the default auto-login method?

[jpeters]

Maybe alu's not having the same issue that I had, then.  But it still sounds like a permissions problem.  Are you using the default auto-login method?

no, I remastered. I don't know if that makes a difference.  I ran an old copy of tc_1x with autologin, and got a slightly different mixture of tty permissions: tty0 and tty2 were tc:staff, and the others were root:staff.  I guess it (tty1) adjusts to whatever is needed for the initial login.  
I can experiment with different logins, since I don't have a clue as to how it works.  

edit:  I reproduced the error by logging in as "root",  which gives /dev/tty1 permission of root:root that screen doesn't allow without X ( error: cannot open terminal /dev/tty1).  If I login with any other local user, it's fine.  The problem only occurs without X.  
(note: I guess the auto-login is root, as you said).