Bug 416235

Summary: Session restore happens too early, before required servies are started
Product: [Plasma] ksmserver Reporter: Sektor van Skijlen <ethouris>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description Sektor van Skijlen 2020-01-14 10:01:14 UTC
SUMMARY


STEPS TO REPRODUCE
1. Have KDE running
2. Have Konsole started and configured external menu service
3. Restart KDE

OBSERVED RESULT

The Konsole program has started as per session restoration, however it has the menu in itself, despite that the menu widget is already running. When the Konsole window is closed and started again, the menu this time appears in the menu widget only.

EXPECTED RESULT

The program started as per session restoration should have the menu displayed in the menu widget. If the menu widget and associated service isn't ready at this moment, the session restoration process should be delayed until it is ready.

NOTE: This problem is not only about Konsole and menu widget, it's more general. The session restoration happens at the moment when various services are only about to start or are in progress. It was happening earlier also that the session restoration happened before the composition was started, which made the transparent-background windows start with transparency off when started too early. This one fortunately doesn't happen to me anymore, but it looks like the problem, if solved, was only solved partially. I personally don't think it would make KDE any slower start if simply the session restoration is always ran as the exactly very last thing during the startup (when starting earlier, everything slows down anyway due to the load).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15.1
KDE Plasma Version:  5.12.8
KDE Frameworks Version: 5.55
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2020-01-31 21:56:46 UTC

*** This bug has been marked as a duplicate of bug 415781 ***