Bug 1040518

Summary: applications not remembered on session-restore
Product: [Fedora] Fedora Reporter: pgaltieri <pgaltieri>
Component: mate-session-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, rdieter, stefano
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: 2015-02-17 19:36:39 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:

Description pgaltieri 2013-12-11 14:50:52 UTC
Description of problem:
In mate-session-manager startup applications I have the "Automatically remember running applications when logging out" option selected.  This option does not work correctly.  Not all applications are restored when I log back in.

Version-Release number of selected component (if applicable):
mate-session-manager.x86_64            1.6.1-4.fc19 

How reproducible:
Always happens

Steps to Reproduce:
1. Enabled the remember option under "Startup Applications"
2. Start mate-system-monitor, gnome-terminal, aisleriot, and mate-terminal on
different virtual desktops.
3. Logout
4. Login again

Actual results:
mate-system-monitor, gnome-terminal, aisleriot are not started.  Sometimes only a subset of the mate-terminals I had running prior to logging out are restored, and sometimes some mate-terminals appear on wrong desktop. 

Expected results:
All applications are restarted

Additional info:
This is similar to bug 967715 which is filed against gnome.

Comment 1 Wolfgang Ulbrich 2013-12-25 06:46:10 UTC
forward to upstream.
https://github.com/mate-desktop/mate-session-manager/issues/42

Comment 2 Wolfgang Ulbrich 2013-12-25 07:10:29 UTC
Pleas ask ther for help.

Comment 3 pgaltieri 2014-01-13 22:44:39 UTC
This response is irresponsible.  I get mate via the fedora release, therefore it is fedora's responsibility to track and correct mate bugs.  It's not my responsibility to hound the mate engineers to fix their problems.  That is Fedora's responsibility.

Comment 4 Wolfgang Ulbrich 2014-01-14 15:38:27 UTC
I said this because those guys can help you better than me, seems you don't like to get help........

PS: All work for mate and helping users i do in my free time.

Comment 5 pgaltieri 2014-02-03 05:53:37 UTC
Well the bug has been sitting with them for over a month now with no action, so they aren't being very helpful either.

Comment 6 Fedora End Of Life 2015-01-09 20:50:11 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 7 Fedora End Of Life 2015-02-17 19:36:39 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.