screen fails with “WriteMessage: Bad file descriptor”
Clash Royale CLAN TAG#URR8PPP
I have screen session "main", started in /dev/ttySAC0 and sh, started in /dev/ttySAC0 (outside screen session) with input, output and error streams, redirected to pseudoterminal /dev/pts/1.
When I attach to /dev/pts/1 terminal and try to run screen -r main, it fails with:
WriteMessage: Bad file descriptor
But creating new screen session with screen works fine. Furthermore, if I run screen -r main in this screen session, I got screen with my saved session in another screen session. It's not usefull, but it's works.
Even if I starts new session in /dev/pts/1, detatch from it and try to revive it, I got same error.
gnu-screen
asked Dec 17 '15 at 6:55
PabokaPaboka
3314
add a comment |
I have screen session "main", started in /dev/ttySAC0 and sh, started in /dev/ttySAC0 (outside screen session) with input, output and error streams, redirected to pseudoterminal /dev/pts/1.
When I attach to /dev/pts/1 terminal and try to run screen -r main, it fails with:
WriteMessage: Bad file descriptor
But creating new screen session with screen works fine. Furthermore, if I run screen -r main in this screen session, I got screen with my saved session in another screen session. It's not usefull, but it's works.
Even if I starts new session in /dev/pts/1, detatch from it and try to revive it, I got same error.
gnu-screen
asked Dec 17 '15 at 6:55
PabokaPaboka
3314
add a comment |
I have screen session "main", started in /dev/ttySAC0 and sh, started in /dev/ttySAC0 (outside screen session) with input, output and error streams, redirected to pseudoterminal /dev/pts/1.
When I attach to /dev/pts/1 terminal and try to run screen -r main, it fails with:
WriteMessage: Bad file descriptor
But creating new screen session with screen works fine. Furthermore, if I run screen -r main in this screen session, I got screen with my saved session in another screen session. It's not usefull, but it's works.
Even if I starts new session in /dev/pts/1, detatch from it and try to revive it, I got same error.
gnu-screen
asked Dec 17 '15 at 6:55
PabokaPaboka
3314
I have screen session "main", started in /dev/ttySAC0 and sh, started in /dev/ttySAC0 (outside screen session) with input, output and error streams, redirected to pseudoterminal /dev/pts/1.
When I attach to /dev/pts/1 terminal and try to run screen -r main, it fails with:
WriteMessage: Bad file descriptor
But creating new screen session with screen works fine. Furthermore, if I run screen -r main in this screen session, I got screen with my saved session in another screen session. It's not usefull, but it's works.
Even if I starts new session in /dev/pts/1, detatch from it and try to revive it, I got same error.
gnu-screen
gnu-screen
asked Dec 17 '15 at 6:55
PabokaPaboka
3314
asked Dec 17 '15 at 6:55
PabokaPaboka
3314
asked Dec 17 '15 at 6:55
PabokaPaboka
3314
asked Dec 17 '15 at 6:55
PabokaPaboka
3314
asked Dec 17 '15 at 6:55
PabokaPaboka
3314
3314
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Run screen -d, find the screens and run screen -R [screen_name].
edited Feb 16 '18 at 8:11
Stephen Kitt
171k24386462
answered Feb 16 '18 at 7:53
sudhanshusudhanshu
411
add a comment |
Try adding the line defnonblock on to your ~/.screenrc file.
When I began having the same problem I found a few posts mentioning that it fixed their issues. It fixed mine.
answered Jul 4 '16 at 19:13
Anthony DawsonAnthony Dawson
312
It didn't help.
– Paboka
Feb 13 '17 at 5:29
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f249907%2fscreen-fails-with-writemessage-bad-file-descriptor%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Run screen -d, find the screens and run screen -R [screen_name].
edited Feb 16 '18 at 8:11
Stephen Kitt
171k24386462
answered Feb 16 '18 at 7:53
sudhanshusudhanshu
411
add a comment |
Run screen -d, find the screens and run screen -R [screen_name].
edited Feb 16 '18 at 8:11
Stephen Kitt
171k24386462
answered Feb 16 '18 at 7:53
sudhanshusudhanshu
411
add a comment |
Run screen -d, find the screens and run screen -R [screen_name].
edited Feb 16 '18 at 8:11
Stephen Kitt
171k24386462
answered Feb 16 '18 at 7:53
sudhanshusudhanshu
411
Run screen -d, find the screens and run screen -R [screen_name].
edited Feb 16 '18 at 8:11
Stephen Kitt
171k24386462
answered Feb 16 '18 at 7:53
sudhanshusudhanshu
411
edited Feb 16 '18 at 8:11
Stephen Kitt
171k24386462
edited Feb 16 '18 at 8:11
Stephen Kitt
171k24386462
edited Feb 16 '18 at 8:11
Stephen Kitt
171k24386462
171k24386462
answered Feb 16 '18 at 7:53
sudhanshusudhanshu
411
answered Feb 16 '18 at 7:53
sudhanshusudhanshu
411
answered Feb 16 '18 at 7:53
sudhanshusudhanshu
411
411
add a comment |
add a comment |
Try adding the line defnonblock on to your ~/.screenrc file.
When I began having the same problem I found a few posts mentioning that it fixed their issues. It fixed mine.
answered Jul 4 '16 at 19:13
Anthony DawsonAnthony Dawson
312
It didn't help.
– Paboka
Feb 13 '17 at 5:29
add a comment |
Try adding the line defnonblock on to your ~/.screenrc file.
When I began having the same problem I found a few posts mentioning that it fixed their issues. It fixed mine.
answered Jul 4 '16 at 19:13
Anthony DawsonAnthony Dawson
312
It didn't help.
– Paboka
Feb 13 '17 at 5:29
add a comment |
Try adding the line defnonblock on to your ~/.screenrc file.
When I began having the same problem I found a few posts mentioning that it fixed their issues. It fixed mine.
answered Jul 4 '16 at 19:13
Anthony DawsonAnthony Dawson
312
Try adding the line defnonblock on to your ~/.screenrc file.
When I began having the same problem I found a few posts mentioning that it fixed their issues. It fixed mine.
answered Jul 4 '16 at 19:13
Anthony DawsonAnthony Dawson
312
answered Jul 4 '16 at 19:13
Anthony DawsonAnthony Dawson
312
answered Jul 4 '16 at 19:13
Anthony DawsonAnthony Dawson
312
answered Jul 4 '16 at 19:13
Anthony DawsonAnthony Dawson
312
312
It didn't help.
– Paboka
Feb 13 '17 at 5:29
add a comment |
It didn't help.
– Paboka
Feb 13 '17 at 5:29
It didn't help.
– Paboka
Feb 13 '17 at 5:29
It didn't help.
– Paboka
Feb 13 '17 at 5:29
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f249907%2fscreen-fails-with-writemessage-bad-file-descriptor%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown