Bug 504588

Summary: Dolphin new window duplicates existing tabs
Product: [Applications] dolphin Reporter: andy <andy>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: john.kizer, kfm-devel
Priority: NOR    
Version First Reported In: 25.04.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description andy 2025-05-20 23:55:46 UTC
SUMMARY
When you already have a Dolphin window open with some tabs, in different scenarios when opening a new Dolphin window (manually, via an app, xdg-open, via mounting USB drive) dolphin opens a new window that may or may not duplicate the same tabs in the pre-existing window.

STEPS TO REPRODUCE
1. Have open a Dolphin window with several tabs open
2. Try opening a new Dolphin window from different sources

OBSERVED RESULT
- [pass] Firefox downloads: > Show in Folder: opens a new dolphin window with a single tab open to downloads
- [fail] Application launcher > Dolphin: opens a new dolphin window with the same tabs open as previous window
- [fail] go to 2nd or 3rd desktop and click the dolphin icon on the task manager: opens new Dolphin window with same tabs as previous
- [fail] Insert USB drive > click Mount and Open button: opens new Dolphin window with same tabs as previous


EXPECTED RESULT
All the above should open a new window either to a specific folder (in the case of "Show in folder"), or open a new dolphin window to a default location like Home. But if there are no Dolphin instances open, yes that is when it should remember what tabs were opened last.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Arch Linux 6.14.6-arch1-1 (64-bit)
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
The new Wayland session restore is also a bit odd, I don't think it handles multiple windows correctly in general for any app. I had to turn it off.
Comment 1 John Kizer 2025-05-26 05:22:48 UTC
Hi - merging this in with the existing report for this issue. Thanks!

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