https://bugs.kde.org/show_bug.cgi?id=502770
--- Comment #43 from Rafael Linux User <rafael.linux.u...@gmail.com> --- (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 -- You are receiving this mail because: You are watching all bug changes.
