| Summary: | Load a default session that can be saved on application closure, so session saving is automatic like a web browser | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Mike Robinson <kde_bugs> |
| Component: | sessions | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | andrew.crouthamel, barney.b, bugseforuns, christoph, ddascalescu+kde, jamesxmcintosh, KDE, kde, kde_bug_tracking, marekful, michal.humpula, mmegibb, nate, nortexoid, waqar.17a |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/utilities/kate/-/commit/88c6ab08f48fd3c088470716a1d175496a3960d2 | Version Fixed In: | 21.12 |
| Sentry Crash Report: | |||
|
Description
Mike Robinson
2011-03-19 20:42:19 UTC
Somehow I fixed the problem. I clicked on Sessions > Quick open session > default (which was the only option) and it loaded a session that was saved from before the kde 4.6 upgrade and now it works as expected. Also, before this was fixed, I noticed that the "recent documents" were not saving either. Hopefully this helps someone trying to debug this error. If that works for you now, that is fine, I guess we won't find there any error, as we can't reproduce, too. This bug actually still exists for me even after OS reinstall. When telling kate to remember the last session, the "Last Session" variable of ~/.kde/share/config/katerc should change from blank to "mysession.katesession", but this doesn't happen, so when you open up kate, it always starts with a new window. I tried manually editing the above file with that value, but upon one of the updates it got overwritten again. See the following question I opened on askubuntu: http://askubuntu.com/questions/57855/how-do-i-get-kate-to-restore-last-used-session Another way to reproduce this bug: 1) In ~/.kde/share/config/katerc change the Last Session line to "Last Session=" with nothing after it 2) Open Kate and set it to remember "load last-used session" (if it isn't already) 3) Open a file with Kate and close and reopen the window Hi Mike, do you still experie this problem with current version of kate? Yes, I am still having the same problem with Kubuntu 13.10: KDE 4.11.3 and Kate 3.11.3. Hi Mike, the session workflow changed a little bit trough time (there is no explicit default session now). I've noticed that you don't select any session specificaly in your "steps to reproduce". If you just start kate to new session, open files and then quit kate, the last session will be none, i.e. the new (unnamed) session doesn't count in this case. You have to quit kate with named/saved session. Is this the case you are describing? Hi Michal, Thank you for your reply. I think Kate is a bit misleading then. If I tell my web browser to resume the last used session, it opens up my previous tabs. If I tell KDE to restore my previous session (Settings > Session Management), it opens up my previously used windows when I log in again. I would expect that when Kate says "Load last-used session", it would open up all the previous files that were open when Kate was closed. However, if the desired behavior is to have the user first create a session and then save it and only then can it be resumed, perhaps some sort of error message should appear when the "last-used" session is not available. Hi from the Bugsquad! I am going to change this severity to wishlist since the reporter can make this function, but has to create a session first. I can confirm the session loading works, but agree it is confusing. This is a bug, and not a wish! I came here today because I wanted to file a bug about exactly this totally unexpected behavior of Kate and first searched if it is already reported. It is reported 5 times, exactly this or a closely related bad behavior, the first reports dating back to the year 2011 and 2013. Calling it a wish because someone might by chance find some hidden workaround is not helpful for the user. The repeated reports clearly show this. Classifying it a wish might be good to fake the statistics about KDE software related bugs to look better, though. But calling it a wish does not resolve the bad behavior and only pushes it deeper into the state of "will never be cared for". As you can read, upon reading the last comment, my mood changed from "Hmmm, I should spent some time to write a helpful bug report" to "I like KDE PLASMA and will continue to use it, but it might be better to not expect the KDE applications to receive support and before even loosing time to write a bug report simply stay with other solutions, like in this case Geany". However, as I have the other report numbers already at hand, here they are: https://bugs.kde.org/show_bug.cgi?id=268913 (this one, from 2011!) https://bugs.kde.org/show_bug.cgi?id=319396 (from 2013) https://bugs.kde.org/show_bug.cgi?id=342057 (from 2014) https://bugs.kde.org/show_bug.cgi?id=332949 (from 2014) https://bugs.kde.org/show_bug.cgi?id=382906 (from 2017) I wanted to write all this from those 5 reports in my own bug report, but as all this is already reported, I should not do so. Now I am unsure. Maybe I have to report it as a new bug, so that after so many years this strange and not expected behavior once might receive attention. I am using on Debian 9.5 (currently the stable Debian edition): Kate 16.08.3 KDE Frameworks 5.28.0 Qt 5.7.1 (built against 5.7.1) The xcb windowing system *** This bug has been marked as a duplicate of bug 319396 *** *** Bug 402598 has been marked as a duplicate of this bug. *** Isn't 418183 also a duplicate? *** Bug 418183 has been marked as a duplicate of this bug. *** Fixed by Michal Humpula with https://invent.kde.org/utilities/kate/-/commit/88c6ab08f48fd3c088470716a1d175496a3960d2 in Kate 21.12! *** Bug 433237 has been marked as a duplicate of this bug. *** *** Bug 332949 has been marked as a duplicate of this bug. *** Not working for me on a clean install of version 22.04.3 of Kate (on Manjaro). I had to save the session first before it would load it on startup. |