| Summary: | Kate cannot restore its session | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Chusslove Illich <caslav.ilic> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.2 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Immediate initialization of session config in kdebase/kate/app/katemain.cpp | ||
|
Description
Chusslove Illich
2004-02-08 13:56:38 UTC
Created attachment 4597 [details]
Immediate initialization of session config in kdebase/kate/app/katemain.cpp
I've poked some more... In KApplication::sessionConfigName(), function
sessionKey() reports the wrong string. However, KApplication::sessionConfig()
will not initialize session config again once already initialized, and
sessionKey() still reports correct value right after declaration "KateApp app;"
in kdebase/kate/app/katemain.cpp, so the problem is dirty-solved by calling
"app.sessionConfig();" right after declaration. The patch is attached.
Confirming. This is a really annoying bug, esp. with 20 files open for development. true ;) perhaps I should have read even the comment from 09.02 ;), would have not wasted my time with figuring that out myself ;) (but in the end, had some good results, have rewritten the rest of session restore, too) backport is now in KDE_3_2_BRANCH, therefor will be in kde 3.2.1 ;) |