Byobu cache or restored duplicate sessionshow to run multiple byobu sessions at once?Use multiple byobu sessions, while ignoring unrelated tmux sessionsByobu weird characterByobu, empty windows namesWhen exiting Byobu, close all non-exited vim sessionsByobu: kill warningByobu tmux pane bordersByobu skeleton files?Switch byobu session quickly?Is there a way to tell byobu to use $HOME/.cache/byobu instead of /dev/shm/ even though I have /dev/shm available?

Intuition behind counterexample of Euler's sum of powers conjecture

'The literal of type int is out of range' con número enteros pequeños (2 dígitos)

Plausibility of Mushroom Buildings

What are some noteworthy "mic-drop" moments in math?

How are showroom/display vehicles prepared?

Counting all the hearts

In the late 1940’s to early 1950’s what technology was available that could melt a LOT of ice?

Error during using callback start_page_number in lualatex

What Happens when Passenger Refuses to Fly Boeing 737 Max?

How do I express some one as a black person?

What is the magic ball of every day?

Filtering SOQL results with optional conditionals

Why does Captain Marvel assume the people on this planet know this?

How strictly should I take "Candidates must be local"?

Could you please stop shuffling the deck and play already?

Virginia employer terminated employee and wants signing bonus returned

Why does the negative sign arise in this thermodynamic relation?

How to draw cubes in a 3 dimensional plane

Can you reject a postdoc offer after the PI has paid a large sum for flights/accommodation for your visit?

Does this video of collapsing warehouse shelves show a real incident?

Do items de-spawn in Diablo?

Was Luke Skywalker the leader of the Rebel forces on Hoth?

What problems would a superhuman have whose skin is constantly hot?

PTIJ: Should I kill my computer after installing software?



Byobu cache or restored duplicate sessions


how to run multiple byobu sessions at once?Use multiple byobu sessions, while ignoring unrelated tmux sessionsByobu weird characterByobu, empty windows namesWhen exiting Byobu, close all non-exited vim sessionsByobu: kill warningByobu tmux pane bordersByobu skeleton files?Switch byobu session quickly?Is there a way to tell byobu to use $HOME/.cache/byobu instead of /dev/shm/ even though I have /dev/shm available?













6















Every time I quit Byobu accidentally, on the next start I find an extra session tab for each session called _sessionname-id:



screenshotscreenshot



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.










share|improve this question
























  • 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
    2 hours ago















6















Every time I quit Byobu accidentally, on the next start I find an extra session tab for each session called _sessionname-id:



screenshotscreenshot



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.










share|improve this question
























  • 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
    2 hours ago













6












6








6


2






Every time I quit Byobu accidentally, on the next start I find an extra session tab for each session called _sessionname-id:



screenshotscreenshot



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.










share|improve this question
















Every time I quit Byobu accidentally, on the next start I find an extra session tab for each session called _sessionname-id:



screenshotscreenshot



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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 hours ago









Pablo Bianchi

2,90521535




2,90521535










asked Jun 20 '17 at 1:28









IlliaxIlliax

814




814












  • 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
    2 hours ago

















  • 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
    2 hours ago
















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
2 hours ago





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
2 hours ago










1 Answer
1






active

oldest

votes


















0














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.






share|improve this answer




















  • 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 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





    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










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
);



);













draft saved

draft discarded


















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









0














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.






share|improve this answer




















  • 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 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





    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















0














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.






share|improve this answer




















  • 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 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





    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













0












0








0







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.






share|improve this answer















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.







share|improve this answer














share|improve this answer



share|improve this answer








edited 7 hours ago









Pablo Bianchi

2,90521535




2,90521535










answered Jun 27 '17 at 20:18









dgonzalezdgonzalez

4,16541124




4,16541124







  • 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 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





    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





    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 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





    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

















draft saved

draft discarded
















































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.




draft saved


draft discarded














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





















































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







Popular posts from this blog

Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

Torre de la Isleta Índice Véase también Referencias Bibliografía Enlaces externos Menú de navegación38°25′58″N 0°23′02″O / 38.43277778, -0.3838888938°25′58″N 0°23′02″O / 38.43277778, -0.38388889Torre de la Illeta de l’Horta o Torre Saleta. Base de datos de bienes inmuebles. Patrimonio Cultural. Secretaría de Estado de CulturaFicha BIC Torre de la Illeta de l’Horta. Dirección General de Patrimonio Cultural. Generalitat ValencianaLugares de interés. Ayuntamiento del CampelloTorre de la Isleta en CastillosNet.org