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

--- Comment #7 from Sergey Katunin <[email protected]> ---
(In reply to Nate Graham from comment #6)
> So, looking at the reported problems:
>     
> > Restored only one window for Kate without state (welcome page).
> This is expected. It can only be fixed by the toolkit and app opting into
> the Wayland session restore protocol. KWin gained support for it in Plasma
> 6.7 (see Bug 436318), but now it's up to toolkits and apps to opt in.
> 
> You can also work around it in Kate itself by using the Sessions feature;
> this way, Kate itself remembers what files were open last time, even without
> the compositor doing any session management of its own.
>  
>  > Restored only one window (instance) for Dolphin.
> Same problem as Kate; the app would need to opt into the Wayland session
> management protocol.
> 
> So I would recommend that you open bug reports for apps that need to restore
> their actual state — as opposed to just re-launching — and request that they
> implement support for the Wayland session restore protocol.
> 
> > Gwenview is not restored at all.
> This is a bug; let's track it here. But I'm not able to reproduce it.
> Gwenview launches as expected, and the contents of
> ~/.local/state/plasmasessionrestorestaterc are what I expect, too:
> 
> [0]
> appId=org.kde.kate.desktop
> 
> [1]
> appId=org.kde.dolphin.desktop
> 
> [3]
> appId=org.kde.gwenview.desktop
> 
> Tracey and Sergey, what does that file say after a restart in which Gwenview
> was open at restart time but failed to launch after login?

For Gwenview this file says:

[7]
appId=org.kde.gwenview_importer.desktop

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to