Bug 503005

Summary: Dolphin wipes the tabs session if launched via mounting an Android device (MTP)
Product: [Applications] dolphin Reporter: kdeuzver <asdf-kd>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: dolphin-bugs-null, john.kizer
Priority: NOR    
Version First Reported In: 24.12.3   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kdeuzver 2025-04-19 06:32:33 UTC 
SUMMARY
If you run Dolphin over the mtp: protocol when you mounting an Android device from a popup, the session of previously open tabs will be wiped.

STEPS TO REPRODUCE
1. Connect Android device via USB
2. When popup appear click to mount

OBSERVED RESULT
Dolphin opens with 1 tab, all other tabs from the last session wiped out

EXPECTED RESULT
Dolphin always keep the session!

SOFTWARE/OS VERSIONS
Linux: KDE Neon 6.3
Dolphin 24.12.3
Operating System: KDE neon 6.3
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.3
Kernel Version: 6.11.0-24-generic (64-bit)
Graphics Platform: Wayland
Processors: 22 × Intel® Core™ Ultra 7 155H
Memory: 31.0 ГиБ of RAM
Graphics Processor: Intel® Arc

ADDITIONAL INFORMATION
Comment 1 John Kizer 2025-04-21 17:13:38 UTC 
Hi - are the open tabs in Dolphin also being lost if you simply close and reopen Dolphin from the application launcher, regardless of whether an MTP device is involved?
Comment 2 kdeuzver 2025-04-26 01:37:08 UTC 
(In reply to John Kizer from comment #1)
> Hi - are the open tabs in Dolphin also being lost if you simply close and
> reopen Dolphin from the application launcher, regardless of whether an MTP
> device is involved?

Damn, now it wipes even via launcher.
I guess I didn't notice it right away. Apparently some recent update brought it in. That's sad.
Comment 3 John Kizer 2025-04-26 02:05:15 UTC 
The good news is that, since it's that overall issue, it's already identified with a fix coming in KDE Gear version 25.04.1 :-)

A workaround is identified https://bugs.kde.org/show_bug.cgi?id=502770#c20 in the meantime, if needed.

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