Bug 428163 - yakuake: Session restore not always working
Summary: yakuake: Session restore not always working
Status: RESOLVED FIXED
Alias: None
Product: yakuake
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-24 03:41 UTC by pat_h
Modified: 2020-10-27 04:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pat_h 2020-10-24 03:41:38 UTC
SUMMARY
Although session restore is generally active here, sometimes yakuake starts on login and sometimes not. I could not observe a pattern, yet.

STEPS TO REPRODUCE
1. Activate session restore
2. Start yakuake
3. Log out
4. Log in

OBSERVED RESULT
Sometimes yakuake gets started sometimes not

EXPECTED RESULT
yakuake gets always started

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.8.0-3-amd64
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 11,6 GiB
 
ADDITIONAL INFORMATION
I guess that it is either a session saving or session loading problem. If I knew in which file the yakuake session is stored to (I assume it's only the starting information and not more currently), I could check if saving works. This might reduce the problem search space at least a bit.
Comment 1 Nate Graham 2020-10-26 15:27:42 UTC
> KDE Plasma Version: 5.17.5
This version is no longer supported upstream. Does the problem still happen with Plasma 5.18 (the LTS version) or 5.20 (the latest version)?
Comment 2 pat_h 2020-10-27 04:50:05 UTC
Thanks for the hint, Nate! It didn't completely trace it down (it's hard as it's not completely reproducible), but it looks like the upgrade from KDE Frameworks from 5.70.0 to 5.74.0 fixed it.

During the last weeks I think I had the problem in more than 50% of the log-ins. I couldn't reproduce it after the upgrade while trying four times.

So I'll close the bug. If it reappears, I'll reopen.

Kind regards
Patrick