Created attachment 180241 [details] Dolphin forgetting open tabs SUMMARY After the Frameworks 6.13 update, Dolphin no longer reopens folders and tabs from the last time it was open. Instead, it opens a single tab with whatever folder is shown in the editable textbox next to the second "Show on startup" radio button. STEPS TO REPRODUCE 1. Open Dolphin 2. Click Settings > Configure Dolphin... > Interface > Folders & Tabs 3. In the "Show on startup" section, choose "Folders, tabs, and window state from last time" 4. Click OK 5. Open multiple additional tabs in that existing Dolphin window 6. Close Dolphin 7. Open Dolphin OBSERVED RESULT The Dolphin window contains a single tab, with whatever folder is shown in the editable textbox next to the second "Show on startup" radio button. EXPECTED RESULT Dolphin reopens the tabs that were opened in step 5. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 41 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION This might belong in a Frameworks product, but I wasn't sure which one was applicable here. The issue began as soon as Frameworks 6.13.0 was installed - on the system where that upgrade was performed "online", the issue began immediately after the kf6 package updates, before any reboots. Nothing too noticeable stuck out to me in the terminal output from dolphin: johnkizer@g717-fedora:~$ dolphin qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x89 0x50 qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x89 0x50 kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError kf.kio.core: An error occurred during write. The worker terminates now. QThreadStorage: Thread 0x562984088010 exited after QThreadStorage 8 destroyed QThreadStorage: Thread 0x562984088010 exited after QThreadStorage 2 destroyed QThreadStorage: Thread 0x562984088010 exited after QThreadStorage 1 destroyed qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x89 0x50 qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x89 0x50 QThreadStorage: Thread 0x55f29dd48b90 exited after QThreadStorage 9 destroyed johnkizer@g717-fedora:~$ dolphin qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x89 0x50 qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x89 0x50 QThreadStorage: Thread 0x55c3386c9b90 exited after QThreadStorage 9 destroyed
Caused by https://invent.kde.org/frameworks/kxmlgui/-/commit/8c9fb02a1d37672b26a03a9dd9e8675743deb269
*** Bug 502781 has been marked as a duplicate of this bug. ***
Thanks for the lead! Just to confirm, this is also occurring on my device on a version of Dolphin (and its dependencies) built from git master.
*** Bug 502773 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/950
Git commit c0bf226aa1cc02c9bffff1ec05e07a255d8d2f6e by Felix Ernst, on behalf of Felix Ernst. Committed on 16/04/2025 at 13:27. Pushed by felixernst into branch 'master'. Fix session restore Since https://commits.kde.org/kxmlgui/8c9fb02a1d37672b26a03a9dd9e8675743deb269 KXmlGui only triggers a session restore for a window when the session config contains a "NumberOfWindows" key with a value >= 1. This commit adds such a key to the Dolphin session config, which fixes the Dolphin main window restore for KXmlGui versions containing that commit. M +2 -0 src/dolphinmainwindow.cpp https://invent.kde.org/system/dolphin/-/commit/c0bf226aa1cc02c9bffff1ec05e07a255d8d2f6e
Git commit 6032b78512685dc7d6cc3754d536823d428525c4 by Felix Ernst, on behalf of Felix Ernst. Committed on 16/04/2025 at 13:50. Pushed by felixernst into branch 'release/25.04'. Fix session restore Since https://commits.kde.org/kxmlgui/8c9fb02a1d37672b26a03a9dd9e8675743deb269 KXmlGui only triggers a session restore for a window when the session config contains a "NumberOfWindows" key with a value >= 1. This commit adds such a key to the Dolphin session config, which fixes the Dolphin main window restore for KXmlGui versions containing that commit. (cherry picked from commit c0bf226aa1cc02c9bffff1ec05e07a255d8d2f6e) Co-authored-by: Felix Ernst <felixernst@zohomail.eu> M +2 -0 src/dolphinmainwindow.cpp https://invent.kde.org/system/dolphin/-/commit/6032b78512685dc7d6cc3754d536823d428525c4
*** Bug 502887 has been marked as a duplicate of this bug. ***
*** Bug 502922 has been marked as a duplicate of this bug. ***
Was this fix was merged into 25.04? For me this issue is still present in version 25.04 with KDE Framework 6.13 OpenSuse TW with KDE repo. Dolphin: 25.04.0 KDE Frameworks: 6.13.0 Qt: 6.9.0 openSUSE Tumbleweed (Wayland) Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.14.2-1-default
*** Bug 503001 has been marked as a duplicate of this bug. ***
(In reply to Jacek from comment #11) > Was this fix was merged into 25.04? For me this issue is still present in > version 25.04 with KDE Framework 6.13 I merged it into the 25.04 immediately, but unfortunately this was already many days too late for the initial release 25.04.0. The fix is going to be released in Dolphin 25.04.1 though. I have now added this information to the "Version Fixed In" field at the top of this page. I have not caused this bug, but I know it sucks that session restore is broken for the moment. Sorry for the inconvenience.
For others who find their way here and would like a workaround before that fix lands: Close dolphin first, then: echo -e '\n[Number]\nNumberOfWindows=1\n' >> ~/.config/session/dolphin_dolphin_dolphin Hope that helps and thanks for the fix Felix!
(In reply to pallaswept from comment #14) > For others who find their way here and would like a workaround before that > fix lands: > > Close dolphin first, then: > echo -e '\n[Number]\nNumberOfWindows=1\n' >> > ~/.config/session/dolphin_dolphin_dolphin > > Hope that helps and thanks for the fix Felix! Thank You! You've saved ma sanity!
*** Bug 503045 has been marked as a duplicate of this bug. ***
*** Bug 503110 has been marked as a duplicate of this bug. ***
*** Bug 503123 has been marked as a duplicate of this bug. ***
*** Bug 503131 has been marked as a duplicate of this bug. ***
A slightly cleaner command: kwriteconfig6 --file ~/.config/session/dolphin_dolphin_dolphin --group Number --key NumberOfWindows 1
(In reply to Ilya Bizyaev from comment #20) > A slightly cleaner command: > > kwriteconfig6 --file ~/.config/session/dolphin_dolphin_dolphin --group Number --key NumberOfWindows 1 Thanks Ilya. I wasn't sure if kwriteconfig would be angry if I created an entry that wasn't legit yet. I can't edit my post above but this is better and people should use this and not mine.
*** Bug 503147 has been marked as a duplicate of this bug. ***
*** Bug 503150 has been marked as a duplicate of this bug. ***
*** Bug 503166 has been marked as a duplicate of this bug. ***
*** Bug 503177 has been marked as a duplicate of this bug. ***
*** Bug 503278 has been marked as a duplicate of this bug. ***
*** Bug 503308 has been marked as a duplicate of this bug. ***
*** Bug 503339 has been marked as a duplicate of this bug. ***
I have this bug, too, but I have an older version of dolphin on Nobara OS 41. Guess I have to wait until the update? Or is there anything I can do to fix it?
(In reply to Kalzi from comment #29) > I have this bug, too, but I have an older version of dolphin on Nobara OS > 41. Guess I have to wait until the update? Or is there anything I can do to > fix it? Running the command in comment #20 above fixed it for me.
(In reply to S. Christian Collins from comment #30) > (In reply to Kalzi from comment #29) > > I have this bug, too, but I have an older version of dolphin on Nobara OS > > 41. Guess I have to wait until the update? Or is there anything I can do to > > fix it? > > Running the command in comment #20 above fixed it for me. thanks for the magical solution! hopefully it survives on next boot...
(In reply to hong from comment #31) > (In reply to S. Christian Collins from comment #30) > > (In reply to Kalzi from comment #29) > > > I have this bug, too, but I have an older version of dolphin on Nobara OS > > > 41. Guess I have to wait until the update? Or is there anything I can do to > > > fix it? > > > > Running the command in comment #20 above fixed it for me. > > thanks for the magical solution! > hopefully it survives on next boot... Thank you so much for tagging me in this. It fixed it for me, too
(In reply to S. Christian Collins from comment #30) > (In reply to Kalzi from comment #29) > > I have this bug, too, but I have an older version of dolphin on Nobara OS > > 41. Guess I have to wait until the update? Or is there anything I can do to > > fix it? > > Running the command in comment #20 above fixed it for me. It did for me, too. I appreciate you
*** Bug 503348 has been marked as a duplicate of this bug. ***
*** Bug 503005 has been marked as a duplicate of this bug. ***
*** Bug 503403 has been marked as a duplicate of this bug. ***
(In reply to Ilya Bizyaev from comment #20) > A slightly cleaner command: > > kwriteconfig6 --file ~/.config/session/dolphin_dolphin_dolphin --group > Number --key NumberOfWindows 1 That command "enables" again the feature. But, how to "enable" it and recover my last (about double panel tabs) session I had before this fatal upgrade?
(In reply to Rafael Linux User from comment #37) > That command "enables" again the feature. But, how to "enable" it and > recover my last (about double panel tabs) session I had before this fatal > upgrade? Restore that file ~/.config/session/dolphin_dolphin_dolphin from a backup, while dolphin is not running. Then, run that command kwriteconfig6 --file ~/.config/session/dolphin_dolphin_dolphin --group Number --key NumberOfWindows 1 To fix that session to work in the new version Then when you start dolphin everything will be OK.
(In reply to pallaswept from comment #38) > (In reply to Rafael Linux User from comment #37) > > That command "enables" again the feature. But, how to "enable" it and > > recover my last (about double panel tabs) session I had before this fatal > > upgrade? > > Restore that file > ~/.config/session/dolphin_dolphin_dolphin > from a backup, while dolphin is not running. > > Then, run that command > kwriteconfig6 --file ~/.config/session/dolphin_dolphin_dolphin --group > Number --key NumberOfWindows 1 > To fix that session to work in the new version > > Then when you start dolphin everything will be OK. I'm afraid that in my case it's too late or something wasn't working properly. I have about 10 files that start with "dolphin_alotofnumbers" and one with the name you mentioned. 2.7k May 19, 2022 dolphin_102201b31a5151000165289047800000017440023_1652960154_541677 5.3k Sep 1, 2022 dolphin_102201b31a5151000165881945000000018250094_1662029613_973719 6.2k Nov 29, 2023 dolphin_102201b31a5151000170005813200000027120011_1701245540_929119 3.9k Oct 20, 2021 dolphin_102401d31a5151000162911075500000020200015_1634735854_855828 3.9k Oct 20, 2021 dolphin_102401d31a5151000162911075500000020200015_1634739427_746436 2.2k Sep 29, 2021 dolphin_102401d31a5151000163030973300000027390029_1632933319_386979 1.5k Sep 30, 2021 dolphin_102401d31a5151000163299872200000019150011_1632999998_988546 1.2k Oct 26, 2021 dolphin_102401d31a5151000163482284600000041710013_1635233919_396654 3.8k Nov 26, 2021 dolphin_102401d31a5151000163706751000000018530038_1637935137_745601 11k Apr 28 12:02 dolphin_dolphin_dolphin 11k Apr 28 12:02 dolphin_dolphin_dolphin.backup However, after successfully running "kwriteconfig6 --file ~/.config/session/dolphin_dolphin_dolphin --group Number --key NumberOfWindows 1" and launching Dolphin again, my sessions (7 or 8 with two panels each) are not restored. :(
I tried same in another just upgraded Tumbleweed, but same result. Files are there, but command apparently doesn't restore my previous-to-upgrade Dolphin session :(
Sorry to hear it. It worked for me on Tumbleweed. I restored the file from a snapper btrfs snapshot (I snapshot /home, which is not default in TW) taken before this bug happened, and used the command above, and it worked. It won't work if you have dolphin open (because when you close it, it overwrites the file). I can't imagine what else could be going wrong. If it isn't working, it's maybe because the file you're restoring isn't correct. To be very specific, you need to restore the session file from before the update. On TW, that occurred on 15/04 so restore from 14/04 or earlier. If you do the update, and open dolphin, you will break your session, and then if you run that command, it will not fix the broken session. It will only prevent a non-broken session from becoming broken after the update. But this isn't really the place to discuss your backups, that's a bit offtopic, and every time we post here, we send an email to everyone who had the problem, and scroll the solution further up the page. I'm pretty sure that if you restore the correct file and patch it with the command given in #20 it will work. Good luck!
*** Bug 503498 has been marked as a duplicate of this bug. ***
(In reply to pallaswept from comment #41) > Sorry to hear it. It worked for me on Tumbleweed. I restored the file from a > snapper btrfs snapshot (I snapshot /home, which is not default in TW) taken > before this bug happened, and used the command above, and it worked. > > It won't work if you have dolphin open (because when you close it, it > overwrites the file). I can't imagine what else could be going wrong. If it > isn't working, it's maybe because the file you're restoring isn't correct. > To be very specific, you need to restore the session file from before the > update. On TW, that occurred on 15/04 so restore from 14/04 or earlier. If > you do the update, and open dolphin, you will break your session, and then > if you run that command, it will not fix the broken session. It will only > prevent a non-broken session from becoming broken after the update. > > But this isn't really the place to discuss your backups, that's a bit > offtopic, and every time we post here, we send an email to everyone who had > the problem, and scroll the solution further up the page. I'm pretty sure > that if you restore the correct file and patch it with the command given in > #20 it will work. Good luck! Thank you, I'll not continue then writing here. Anyway, you must know you have reason: My mistake has been that I’m not starting from a "backup" (my data partition has no snapshots), but I really believe the data is there, in the file itself, dolphin_dolphin_dolphin because, in both cases, the size stands out compared to the other files from different dates. Best regards
*** Bug 503507 has been marked as a duplicate of this bug. ***
I’m sorry for sending another message here, but this is really the solution for all those who, like me, don’t have a backup of the contents of the ~/.config/ folder. As I mentioned in my previous email, I found it really strange that the size of my file "dolphin_dolphin_dolphin" was much larger than the other copies, and it was very frustrating to have lost the more than 8 tabs with dual panels that I usually keep open (I manage servers). Well, determined to find out what was in that file, I discovered the simplest solution using a text editor to recover your "lost" tabs without needing backups: 1 - Close Dolphin 2 - Run "kate ~/.config/session/dolphin_dolphin_dolphin" 3 - Search (Ctrl + F) for the text "Tab Data" and go to the last line where that text appears. For example, for me, the last line containing that string was "Tab Data 9=". Take note of the number and add 1 to it. In my case, 10. 4 - Go to the beginning of the file, find the line "Tab Count=", and change the number there to the one you calculated. For me, it became "Tab Count=10". 5 - Save the file 6 - Open Dolphin and magically, all your tabs will reappear. And now, I’ll stay quiet.