Bug 949334

Summary: Session isn't restored for some KDE apps
Product: [Fedora] Fedora Reporter: Andrew <travneff>
Component: kde-workspaceAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dvratil, jgrulich, jreznik, kevin, ltinkl, mbriza, rdieter, rnovacek, ry, smparrish, than, travneff
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:30:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of Kate startup state none

Description Andrew 2013-04-07 20:27:38 UTC 
Created attachment 732425 [details]
Screenshot of Kate startup state

Note: appeared after upgrade F17 -> F18 beta by yum distro-sync.

The problem is that Konsole and Kate don't restore saved session after KDE startup. Konsole just launch with default tab and Kate shows something weird, screenshot attached. Bad parts are highlighted (projects and find-n-replace addons are disabled for the default session but shown there). Activating "Settings" -> "Configure Kate" does nothing.

Don't know how to test other apps.

How to reproduce (almost 100%): doesn't require anything special for me, just relogin to KDE.
Tried some cleanup of ksmserverrc file and sessions dirs, no effect.

KDE 4.10.1-1.fc18.x86_64

Also have this, not sure if matters:
https://bugs.kde.org/show_bug.cgi?id=309280
Comment 1 Andrew 2013-05-01 07:29:07 UTC 
Seems really related to the mentioned kwin crash. I've disabled the logout effect as described in KDE bugzilla and session saving works fine since that.
Comment 2 Martin Bříza 2013-05-02 11:42:54 UTC 
Yes, the session state isn't saved when it's not closed properly.
I think it's related to the upstream feature request I'm linking in the external tracker.
Comment 3 Fedora End Of Life 2013-12-21 12:41:49 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2014-02-05 20:30:25 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.