[Konsole-devel] [konsole] [Bug 346768] After login only one tab is present, when several tabs where opened before logout.

[Stefan Becker]

https://bugs.kde.org/show_bug.cgi?id=346768

--- Comment #7 from Stefan Becker <chemobejk at gmail.com> ---
After some more debugging: I do not think the problem is in konsole, but
somewhere deeper in the stack. When the user selects "Save Session" from the
KMenu the save session code from konsole is called. But If I understand the
debug output I added correctly, then the provided KConfig object is invalid and
therefore will not be saved.

Example 1: konsole without -session

- start:
Session ID   "102262341b6148000143091725100000046460036"
Session Key  ""
-> there is no session information

- "Save Session" event:
SAVE Kconfig address   0xff1aa0
SAVE KConfig name     
"session/konsole_102262341b6148000143091725100000046460036_1430917312_840058"
SAVE KConfig writable  NO
SAVE KConfig isDirty   YES
SAVE KConfig isDirty   NO

Corresponding information saved in ~/.config/ksmserverrc:
session,102262341b6148000143091725100000046460036_1430917312_840058

-> information looks correct, but KConfig isn't writable and not dirty.
Therefore I assume that it isn't written to the disk after all.



Example 2: konsole -session
102262341b6148000143057827700000018470011_1430854163_934517

- start:
Session ID   "102262341b6148000143057827700000018470011"
Session Key  "1430854163_934517"
READ Kconfig address   0x259d270
READ KConfig name     
"session/konsole_102262341b6148000143057827700000018470011_1430854163_934517"
READ KConfig writable  NO
READ KConfig isDirty   YES

-> there is session information, which is restored correctly

- after this session is asked to save itself???? (IMHO this shouldn't happen)
SAVE Kconfig address   0x259d270
SAVE KConfig name     
"session/konsole_102262341b6148000143057827700000018470011_1430854163_934517"
SAVE KConfig writable  NO
SAVE KConfig isDirty   YES
SAVE KConfig isDirty   YES

-> this is the same KConfig object we read from

- "Save Session" event:
SAVE Kconfig address   0x259d270
SAVE KConfig name     
"session/konsole_102262341b6148000143057827700000018470011_1430854163_934517"
SAVE KConfig writable  NO
SAVE KConfig isDirty   NO
SAVE KConfig isDirty   NO

-> it is still the same KConfig object. Again not writable

Corresponding information saved in ~/.config/ksmserverrc:
restartCommand10=src/konsole,-session,102262341b6148000143057827700000018470011_1430917601_970308

-> the session file that ksmserver expected to be written has a different name.


Conclusion: there is something severely wrong with "Saving Session", either for
the whole KF5, or just for KF5kde4libs compatibility (which konsole is using).

-- 
You are receiving this mail because:
You are the assignee for the bug.