Bug 469871 - Dolphin does not startup with the open tabs from last time, instead always starts with the specified folder (not selected)
Summary: Dolphin does not startup with the open tabs from last time, instead always st...
Status: RESOLVED DUPLICATE of bug 469656
Alias: None
Product: dolphin
Classification: Applications
Component: panels: folders (show other bugs)
Version: 23.04.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-16 21:28 UTC by itou.yumeko
Modified: 2023-05-17 01:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description itou.yumeko 2023-05-16 21:28:06 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

Chosen configuration is "Show on startup: Folders, tab, and window state from last time", but dolphin seems to override this with the folder path on the second option to open on a specific location. This happens when just opening dolphin regularly, not just in specific scenarios in the other bug reports.

STEPS TO REPRODUCE
1. Open multiple tabs
2. Ensure the tabs from last time option is selected
3. Close dolphin
4. Open dolphin

OBSERVED RESULT

The location for the unselected startup location option is opened.

EXPECTED RESULT

The tabs open from last time should be open.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.1-arch2-1 (64-bit)

ADDITIONAL INFORMATION

When changing the second specific location option, saving, and observing that this works, switching back to the saved tabs option will open at that changed location of the second option.
Comment 1 Patrick Silva 2023-05-17 01:19:49 UTC

*** This bug has been marked as a duplicate of bug 469656 ***