Dolphin directories are not remembered from previous run (split mode

In split mode views are not remembered from previous run ans reset both every time to the home directory.

Option “At startup : folders, tabs and windowstatus from last time” is enabled

Anyone else experiencing this?

See 502770 – Dolphin does not restore open tabs when "Show on startup" is set to "Folders, tabs, and window state from last time". I fixed this a few hours ago.

2 Likes

So wil be fixed with next KDE Gears release 25.04.

echo -e '\n[Number]\nNumberOfWindows=1\n' >> ~/.config/session/dolphin_dolphin_dolphin

Thanks Felix!

2 Likes

Great!
Looking forward to it!

You have a date for 25.04.1? This error is happening from I upgraded to 25.04.0 (24.12.3 worked well).

Regards

This is public information, the exact date depends on your distro.

We do monthly updates for Plasma, Framework and Gear.

1 Like

Thanks for the info.

Regards

I found in the bug link a nice and working fix (lucking day):

kwriteconfig6 --file ~/.config/session/dolphin_dolphin_dolphin --group Number --key NumberOfWindows 1

Thanks again and the person who made the fix.

Regards

There was in this thread the same workaround (written differently) too.

1 Like

I have the same bug on the latest [today] openSUSE Tumbleweed.

Also, opening dolphin_dolphin_dolphin file shows NumberOfWindows already equals 1.

Read one of the two previous posts that have fixes or update to dolphin 25.04 that fixes it.

Did I not point out that my dolphin_dolphin_dolphin already has Windows = 1?

I am on 25.04.1.

Your response is… non-responsive.

Sorry I missed that.

You should have:

[Number]
NumberOfWindows=1

Under [Number]

It seems it is the case then it is a new issue.
Since 502770 – Dolphin does not restore open tabs when "Show on startup" is set to "Folders, tabs, and window state from last time" has clearly be confirmed as fixed.

I think I identified the issue.

Well, on my machine, it appears to be fixed now. I just did a test reboot and Dolphin remembered the layout. I suspect it was fixed by a major Tumbleweed update yesterday. Perhaps the Tumbleweed maintainers were slow in implementing the fix.

Perhaps we can avoid casting aspersions by viewing the excellent transparent build and QA process:

https://build.opensuse.org/package/show/openSUSE%3AFactory/dolphin
https://openqa.opensuse.org/snapshot-changes/opensuse/Tumbleweed/

The 25.04.1 update (fix) was released on the 7th and was packaged, built, tested and submitted to the automated QA suite by the maintainers on the 9th and passed QA, was approved for release, the snapshot distributed to mirrors and in users’ hands by the 11th, one day prior to your experiencing the issue.

Of course, since there was a known-good workaround in place upstream as far back as 24 days ago, it’s not surprising that nobody has reported the bug to TW to even expect them to have fixed it (they often backport stuff like this)

If anyone was too slow, it wasn’t the TW maintainers :wink:

It did not break here and there are no reports of it breaking on reddit or the opensuse forums. This doesn’t appear to be a tumbleweed problem, more likely something specific to your machine.

I am glad to hear it’s sorted out for you now.

Well, I certainly was not slow - I update every single morning.

And in the end, a lot of breakage is “specific to the machine”, isn’t it? Because no one in the software industry can write code that handles all situations - or in some cases, even most.

You may close this one.