Byobu cache or restored duplicate sessions
Every time I quit Byobu accidentally, on the next start I find an extra session tab for each session called _{sessionname}-{id}:
I find this really annoying since this was not happening in my previous machine with an old Ubuntu 14. I'm on Ubuntu 17.04 now.
Also, i cant find a way to close these extra sessions windows without closing the original.
Pressing F6 (Detach session and then logout) only regenerate the extra/duplicated session with a different {id}.
byobu
edited Mar 11 at 23:50
Pablo Bianchi
2,96021535
asked Jun 20 '17 at 1:28
IlliaxIlliax
814
add a comment |
Every time I quit Byobu accidentally, on the next start I find an extra session tab for each session called _{sessionname}-{id}:
I find this really annoying since this was not happening in my previous machine with an old Ubuntu 14. I'm on Ubuntu 17.04 now.
Also, i cant find a way to close these extra sessions windows without closing the original.
Pressing F6 (Detach session and then logout) only regenerate the extra/duplicated session with a different {id}.
byobu
edited Mar 11 at 23:50
Pablo Bianchi
2,96021535
asked Jun 20 '17 at 1:28
IlliaxIlliax
814
1
Seems this bug. Please set there if the bug also affects you. As stated on official site the place to report bugs is in this Launchpad, not that one (I don't know why that even exist).
– Pablo Bianchi
Mar 11 at 23:52
@PabloBianchi exactly this
– Illiax
Mar 13 at 21:32
1
Possible workaround: Move to "original" session and run:tmux kill-session -t "$(tmux ls | grep _ | tail -1 | cut -f1 -d:)".
– Pablo Bianchi
Mar 14 at 2:00
add a comment |
Every time I quit Byobu accidentally, on the next start I find an extra session tab for each session called _{sessionname}-{id}:
I find this really annoying since this was not happening in my previous machine with an old Ubuntu 14. I'm on Ubuntu 17.04 now.
Also, i cant find a way to close these extra sessions windows without closing the original.
Pressing F6 (Detach session and then logout) only regenerate the extra/duplicated session with a different {id}.
byobu
edited Mar 11 at 23:50
Pablo Bianchi
2,96021535
asked Jun 20 '17 at 1:28
IlliaxIlliax
814
Every time I quit Byobu accidentally, on the next start I find an extra session tab for each session called _{sessionname}-{id}:
I find this really annoying since this was not happening in my previous machine with an old Ubuntu 14. I'm on Ubuntu 17.04 now.
Also, i cant find a way to close these extra sessions windows without closing the original.
Pressing F6 (Detach session and then logout) only regenerate the extra/duplicated session with a different {id}.
byobu
byobu
edited Mar 11 at 23:50
Pablo Bianchi
2,96021535
asked Jun 20 '17 at 1:28
IlliaxIlliax
814
edited Mar 11 at 23:50
Pablo Bianchi
2,96021535
asked Jun 20 '17 at 1:28
IlliaxIlliax
814
edited Mar 11 at 23:50
Pablo Bianchi
2,96021535
edited Mar 11 at 23:50
Pablo Bianchi
2,96021535
edited Mar 11 at 23:50
Pablo Bianchi
2,96021535
2,96021535
asked Jun 20 '17 at 1:28
IlliaxIlliax
814
asked Jun 20 '17 at 1:28
IlliaxIlliax
814
asked Jun 20 '17 at 1:28
IlliaxIlliax
814
814
1
Seems this bug. Please set there if the bug also affects you. As stated on official site the place to report bugs is in this Launchpad, not that one (I don't know why that even exist).
– Pablo Bianchi
Mar 11 at 23:52
@PabloBianchi exactly this
– Illiax
Mar 13 at 21:32
1
Possible workaround: Move to "original" session and run:tmux kill-session -t "$(tmux ls | grep _ | tail -1 | cut -f1 -d:)".
– Pablo Bianchi
Mar 14 at 2:00
add a comment |
1
Seems this bug. Please set there if the bug also affects you. As stated on official site the place to report bugs is in this Launchpad, not that one (I don't know why that even exist).
– Pablo Bianchi
Mar 11 at 23:52
@PabloBianchi exactly this
– Illiax
Mar 13 at 21:32
1
Possible workaround: Move to "original" session and run:tmux kill-session -t "$(tmux ls | grep _ | tail -1 | cut -f1 -d:)".
– Pablo Bianchi
Mar 14 at 2:00
1
1
Seems this bug. Please set there if the bug also affects you. As stated on official site the place to report bugs is in this Launchpad, not that one (I don't know why that even exist).
– Pablo Bianchi
Mar 11 at 23:52
Seems this bug. Please set there if the bug also affects you. As stated on official site the place to report bugs is in this Launchpad, not that one (I don't know why that even exist).
– Pablo Bianchi
Mar 11 at 23:52
@PabloBianchi exactly this
– Illiax
Mar 13 at 21:32
@PabloBianchi exactly this
– Illiax
Mar 13 at 21:32
1
1
Possible workaround: Move to "original" session and run:
tmux kill-session -t "$(tmux ls | grep _ | tail -1 | cut -f1 -d:)".– Pablo Bianchi
Mar 14 at 2:00
Possible workaround: Move to "original" session and run:
tmux kill-session -t "$(tmux ls | grep _ | tail -1 | cut -f1 -d:)".– Pablo Bianchi
Mar 14 at 2:00
add a comment |
1 Answer
1
active
oldest
votes
Seems you are starting it and then exiting it, but keeping the session alive.
You can exit byobu closing the session (logout) at the same time using Shift+F6.
Also, you can switch between sessions using Alt+up andAlt+down, and then close that session panes/windows using Ctrl+D, exit or your preferred method.
You can check byoby's built in help using Shift+F1.
As a brute force approach, you can terminate all byobu's running sessions running byobu kill-server on your terminal before re-running byobu.
Note: Dustin Kirkland, the creator of byobu, has a PPA where you can get newer versions before being released on primary channels.
edited Mar 11 at 18:32
Pablo Bianchi
2,96021535
answered Jun 27 '17 at 20:18
dgonzalezdgonzalez
4,17541124
1
nope. I open any terminal and then type byobu. Than start using it. if i close accidently the terminal and open a new one and then type byobu again : now i have two sessions. But both sessions share the same windows so if i close one window on one sessions, it closes in the other session two. It's like a duplicated session. The problem is if I have 4 sessions and quit, now i have 8 sessions.
– Illiax
Jun 28 '17 at 20:31
how do you "accidentally" close byobu? Do you have byobu enabled at login (F9)? Also, when you said windows, did you refer to byobu-windows created with F2 or window manager windows?
– dgonzalez
Jun 28 '17 at 22:48
by accidentally i mean : alt f4 terminal or ctrl+shift+w on terminal (the terminal tab wich holds byobu) . I don't have byobu enabled at login. Yes, windows means f2 windows.
– Illiax
Jun 29 '17 at 15:35
Ok, I think that's the intended behaviour (if I don't close my shells, keep my session and all processes running). You can always navigate through open sessions withAlt+Up/Down. Also observed (at least on my machines) gnome-terminal asks to confirm closing a terminal with a running process. Anyway you are always able to terminate all byobu's running sessions runningbyobu kill-serveron your terminal prior to re-runningbyobu.
– dgonzalez
Jun 29 '17 at 18:18
1
Ok, seems I'm not able to reproduce your issue. You can also try with last version from Dustin Kirkland's own ppa to see if it's a fixed bug in newer releases.
– dgonzalez
Jun 30 '17 at 19:39
|
show 2 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f927187%2fbyobu-cache-or-restored-duplicate-sessions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Seems you are starting it and then exiting it, but keeping the session alive.
You can exit byobu closing the session (logout) at the same time using Shift+F6.
Also, you can switch between sessions using Alt+up andAlt+down, and then close that session panes/windows using Ctrl+D, exit or your preferred method.
You can check byoby's built in help using Shift+F1.
As a brute force approach, you can terminate all byobu's running sessions running byobu kill-server on your terminal before re-running byobu.
Note: Dustin Kirkland, the creator of byobu, has a PPA where you can get newer versions before being released on primary channels.
edited Mar 11 at 18:32
Pablo Bianchi
2,96021535
answered Jun 27 '17 at 20:18
dgonzalezdgonzalez
4,17541124
1
nope. I open any terminal and then type byobu. Than start using it. if i close accidently the terminal and open a new one and then type byobu again : now i have two sessions. But both sessions share the same windows so if i close one window on one sessions, it closes in the other session two. It's like a duplicated session. The problem is if I have 4 sessions and quit, now i have 8 sessions.
– Illiax
Jun 28 '17 at 20:31
how do you "accidentally" close byobu? Do you have byobu enabled at login (F9)? Also, when you said windows, did you refer to byobu-windows created with F2 or window manager windows?
– dgonzalez
Jun 28 '17 at 22:48
by accidentally i mean : alt f4 terminal or ctrl+shift+w on terminal (the terminal tab wich holds byobu) . I don't have byobu enabled at login. Yes, windows means f2 windows.
– Illiax
Jun 29 '17 at 15:35
Ok, I think that's the intended behaviour (if I don't close my shells, keep my session and all processes running). You can always navigate through open sessions withAlt+Up/Down. Also observed (at least on my machines) gnome-terminal asks to confirm closing a terminal with a running process. Anyway you are always able to terminate all byobu's running sessions runningbyobu kill-serveron your terminal prior to re-runningbyobu.
– dgonzalez
Jun 29 '17 at 18:18
1
Ok, seems I'm not able to reproduce your issue. You can also try with last version from Dustin Kirkland's own ppa to see if it's a fixed bug in newer releases.
– dgonzalez
Jun 30 '17 at 19:39
|
show 2 more comments
Seems you are starting it and then exiting it, but keeping the session alive.
You can exit byobu closing the session (logout) at the same time using Shift+F6.
Also, you can switch between sessions using Alt+up andAlt+down, and then close that session panes/windows using Ctrl+D, exit or your preferred method.
You can check byoby's built in help using Shift+F1.
As a brute force approach, you can terminate all byobu's running sessions running byobu kill-server on your terminal before re-running byobu.
Note: Dustin Kirkland, the creator of byobu, has a PPA where you can get newer versions before being released on primary channels.
edited Mar 11 at 18:32
Pablo Bianchi
2,96021535
answered Jun 27 '17 at 20:18
dgonzalezdgonzalez
4,17541124
1
nope. I open any terminal and then type byobu. Than start using it. if i close accidently the terminal and open a new one and then type byobu again : now i have two sessions. But both sessions share the same windows so if i close one window on one sessions, it closes in the other session two. It's like a duplicated session. The problem is if I have 4 sessions and quit, now i have 8 sessions.
– Illiax
Jun 28 '17 at 20:31
how do you "accidentally" close byobu? Do you have byobu enabled at login (F9)? Also, when you said windows, did you refer to byobu-windows created with F2 or window manager windows?
– dgonzalez
Jun 28 '17 at 22:48
by accidentally i mean : alt f4 terminal or ctrl+shift+w on terminal (the terminal tab wich holds byobu) . I don't have byobu enabled at login. Yes, windows means f2 windows.
– Illiax
Jun 29 '17 at 15:35
Ok, I think that's the intended behaviour (if I don't close my shells, keep my session and all processes running). You can always navigate through open sessions withAlt+Up/Down. Also observed (at least on my machines) gnome-terminal asks to confirm closing a terminal with a running process. Anyway you are always able to terminate all byobu's running sessions runningbyobu kill-serveron your terminal prior to re-runningbyobu.
– dgonzalez
Jun 29 '17 at 18:18
1
Ok, seems I'm not able to reproduce your issue. You can also try with last version from Dustin Kirkland's own ppa to see if it's a fixed bug in newer releases.
– dgonzalez
Jun 30 '17 at 19:39
|
show 2 more comments
Seems you are starting it and then exiting it, but keeping the session alive.
You can exit byobu closing the session (logout) at the same time using Shift+F6.
Also, you can switch between sessions using Alt+up andAlt+down, and then close that session panes/windows using Ctrl+D, exit or your preferred method.
You can check byoby's built in help using Shift+F1.
As a brute force approach, you can terminate all byobu's running sessions running byobu kill-server on your terminal before re-running byobu.
Note: Dustin Kirkland, the creator of byobu, has a PPA where you can get newer versions before being released on primary channels.
edited Mar 11 at 18:32
Pablo Bianchi
2,96021535
answered Jun 27 '17 at 20:18
dgonzalezdgonzalez
4,17541124
Seems you are starting it and then exiting it, but keeping the session alive.
You can exit byobu closing the session (logout) at the same time using Shift+F6.
Also, you can switch between sessions using Alt+up andAlt+down, and then close that session panes/windows using Ctrl+D, exit or your preferred method.
You can check byoby's built in help using Shift+F1.
As a brute force approach, you can terminate all byobu's running sessions running byobu kill-server on your terminal before re-running byobu.
Note: Dustin Kirkland, the creator of byobu, has a PPA where you can get newer versions before being released on primary channels.
edited Mar 11 at 18:32
Pablo Bianchi
2,96021535
answered Jun 27 '17 at 20:18
dgonzalezdgonzalez
4,17541124
edited Mar 11 at 18:32
Pablo Bianchi
2,96021535
edited Mar 11 at 18:32
Pablo Bianchi
2,96021535
edited Mar 11 at 18:32
Pablo Bianchi
2,96021535
2,96021535
answered Jun 27 '17 at 20:18
dgonzalezdgonzalez
4,17541124
answered Jun 27 '17 at 20:18
dgonzalezdgonzalez
4,17541124
answered Jun 27 '17 at 20:18
dgonzalezdgonzalez
4,17541124
4,17541124
1
nope. I open any terminal and then type byobu. Than start using it. if i close accidently the terminal and open a new one and then type byobu again : now i have two sessions. But both sessions share the same windows so if i close one window on one sessions, it closes in the other session two. It's like a duplicated session. The problem is if I have 4 sessions and quit, now i have 8 sessions.
– Illiax
Jun 28 '17 at 20:31
how do you "accidentally" close byobu? Do you have byobu enabled at login (F9)? Also, when you said windows, did you refer to byobu-windows created with F2 or window manager windows?
– dgonzalez
Jun 28 '17 at 22:48
by accidentally i mean : alt f4 terminal or ctrl+shift+w on terminal (the terminal tab wich holds byobu) . I don't have byobu enabled at login. Yes, windows means f2 windows.
– Illiax
Jun 29 '17 at 15:35
Ok, I think that's the intended behaviour (if I don't close my shells, keep my session and all processes running). You can always navigate through open sessions withAlt+Up/Down. Also observed (at least on my machines) gnome-terminal asks to confirm closing a terminal with a running process. Anyway you are always able to terminate all byobu's running sessions runningbyobu kill-serveron your terminal prior to re-runningbyobu.
– dgonzalez
Jun 29 '17 at 18:18
1
Ok, seems I'm not able to reproduce your issue. You can also try with last version from Dustin Kirkland's own ppa to see if it's a fixed bug in newer releases.
– dgonzalez
Jun 30 '17 at 19:39
|
show 2 more comments
1
nope. I open any terminal and then type byobu. Than start using it. if i close accidently the terminal and open a new one and then type byobu again : now i have two sessions. But both sessions share the same windows so if i close one window on one sessions, it closes in the other session two. It's like a duplicated session. The problem is if I have 4 sessions and quit, now i have 8 sessions.
– Illiax
Jun 28 '17 at 20:31
how do you "accidentally" close byobu? Do you have byobu enabled at login (F9)? Also, when you said windows, did you refer to byobu-windows created with F2 or window manager windows?
– dgonzalez
Jun 28 '17 at 22:48
by accidentally i mean : alt f4 terminal or ctrl+shift+w on terminal (the terminal tab wich holds byobu) . I don't have byobu enabled at login. Yes, windows means f2 windows.
– Illiax
Jun 29 '17 at 15:35
Ok, I think that's the intended behaviour (if I don't close my shells, keep my session and all processes running). You can always navigate through open sessions withAlt+Up/Down. Also observed (at least on my machines) gnome-terminal asks to confirm closing a terminal with a running process. Anyway you are always able to terminate all byobu's running sessions runningbyobu kill-serveron your terminal prior to re-runningbyobu.
– dgonzalez
Jun 29 '17 at 18:18
1
Ok, seems I'm not able to reproduce your issue. You can also try with last version from Dustin Kirkland's own ppa to see if it's a fixed bug in newer releases.
– dgonzalez
Jun 30 '17 at 19:39
1
1
nope. I open any terminal and then type byobu. Than start using it. if i close accidently the terminal and open a new one and then type byobu again : now i have two sessions. But both sessions share the same windows so if i close one window on one sessions, it closes in the other session two. It's like a duplicated session. The problem is if I have 4 sessions and quit, now i have 8 sessions.
– Illiax
Jun 28 '17 at 20:31
nope. I open any terminal and then type byobu. Than start using it. if i close accidently the terminal and open a new one and then type byobu again : now i have two sessions. But both sessions share the same windows so if i close one window on one sessions, it closes in the other session two. It's like a duplicated session. The problem is if I have 4 sessions and quit, now i have 8 sessions.
– Illiax
Jun 28 '17 at 20:31
how do you "accidentally" close byobu? Do you have byobu enabled at login (F9)? Also, when you said windows, did you refer to byobu-windows created with F2 or window manager windows?
– dgonzalez
Jun 28 '17 at 22:48
how do you "accidentally" close byobu? Do you have byobu enabled at login (F9)? Also, when you said windows, did you refer to byobu-windows created with F2 or window manager windows?
– dgonzalez
Jun 28 '17 at 22:48
by accidentally i mean : alt f4 terminal or ctrl+shift+w on terminal (the terminal tab wich holds byobu) . I don't have byobu enabled at login. Yes, windows means f2 windows.
– Illiax
Jun 29 '17 at 15:35
by accidentally i mean : alt f4 terminal or ctrl+shift+w on terminal (the terminal tab wich holds byobu) . I don't have byobu enabled at login. Yes, windows means f2 windows.
– Illiax
Jun 29 '17 at 15:35
Ok, I think that's the intended behaviour (if I don't close my shells, keep my session and all processes running). You can always navigate through open sessions with
Alt+Up/Down. Also observed (at least on my machines) gnome-terminal asks to confirm closing a terminal with a running process. Anyway you are always able to terminate all byobu's running sessions running byobu kill-server on your terminal prior to re-running byobu.– dgonzalez
Jun 29 '17 at 18:18
Ok, I think that's the intended behaviour (if I don't close my shells, keep my session and all processes running). You can always navigate through open sessions with
Alt+Up/Down. Also observed (at least on my machines) gnome-terminal asks to confirm closing a terminal with a running process. Anyway you are always able to terminate all byobu's running sessions running byobu kill-server on your terminal prior to re-running byobu.– dgonzalez
Jun 29 '17 at 18:18
1
1
Ok, seems I'm not able to reproduce your issue. You can also try with last version from Dustin Kirkland's own ppa to see if it's a fixed bug in newer releases.
– dgonzalez
Jun 30 '17 at 19:39
Ok, seems I'm not able to reproduce your issue. You can also try with last version from Dustin Kirkland's own ppa to see if it's a fixed bug in newer releases.
– dgonzalez
Jun 30 '17 at 19:39
|
show 2 more comments
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f927187%2fbyobu-cache-or-restored-duplicate-sessions%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
1
Seems this bug. Please set there if the bug also affects you. As stated on official site the place to report bugs is in this Launchpad, not that one (I don't know why that even exist).
– Pablo Bianchi
Mar 11 at 23:52
@PabloBianchi exactly this
– Illiax
Mar 13 at 21:32
1
Possible workaround: Move to "original" session and run:
tmux kill-session -t "$(tmux ls | grep _ | tail -1 | cut -f1 -d:)".– Pablo Bianchi
Mar 14 at 2:00