Bug 487896

Summary: Konsole –tabs-from-file opens additional empty tab
Product: [Applications] konsole Reporter: pizza
Component: tabbarAssignee: Konsole Developer <konsole-devel>
Status: CONFIRMED ---    
Severity: minor CC: baron, kdedev, wenzezlaus
Priority: NOR    
Version: master   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description pizza 2024-06-01 19:07:58 UTC 
SUMMARY
When using '–tabs-from-file' in Konsole, not only the expected tabs configured in the supplied file are opened but an additional empty tab with a regular prompt as well.

STEPS TO REPRODUCE
1. Create a simple text file suitable for `–tabs-from-file` containing pre-configured tabs
2. Start konsole pointing `–tabs-from-file` to that text file

OBSERVED RESULT
For n configured tabs, Konsole always opens n+1 tabs, i.e. one additional empty tab not configured in the file.

EXPECTED RESULT
Only the configured tabs (as defined in the file supplied to `–tabs-from-file`) should open.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Comment 1 Vence 2024-06-03 07:44:02 UTC 
Confirmed
Arch Linux, Plasma 6.0.5, konsole 24.05.0
Comment 2 Vence 2024-06-03 15:14:11 UTC 
As a workaround, use command 

konsole --tabs-from-file `path-to-tabs-file' -e 'bash -c exit'
Comment 3 pizza 2024-06-04 11:47:49 UTC 
(In reply to Vence from comment #2)
> As a workaround, use command 
> 
> konsole --tabs-from-file `path-to-tabs-file' -e 'bash -c exit'

Thank you for confirming and supplying a workaround! In my Kubuntu 22.04, however, appending the exit command still opens the extra tab and also leaves it open, albeit without the prompt being active anymore. So the 'exit' does succeed in ending the shell session but (at least on my Konsole 21.12.3) the tab does not automatically close, so I am still stuck at n+1 tabs.
Comment 4 Kurt Hindenburg 2024-06-05 23:14:02 UTC 
This is a known issue from the start - it wasn't a big deal so wasn't fixed.
Comment 5 Kurt Hindenburg 2024-06-06 23:08:01 UTC 
*** Bug 450018 has been marked as a duplicate of this bug. ***
Comment 6 TraceyC 2024-06-07 18:39:27 UTC 
Marking confirmed since its been experienced by multiple users