Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.11] mate-session-save tool doesn't work right after upgrade from 1.10 #103

Closed
monsta opened this issue Oct 21, 2015 · 7 comments · Fixed by #104
Closed

[1.11] mate-session-save tool doesn't work right after upgrade from 1.10 #103

monsta opened this issue Oct 21, 2015 · 7 comments · Fixed by #104
Milestone

Comments

@monsta
Copy link
Contributor

monsta commented Oct 21, 2015

Steps to reproduce:

  1. Have MATE 1.10 installed.
  2. Upgrade mate-desktop to 1.11 (see https://github.com/mate-desktop/debian-packages/commit/aca038f1235bb2d5801ee56bd69fb277cca0d376).
  3. Upgrade mate-session-manager to 1.11 (also it's better to upgrade mate-settings-daemon to 1.11 at the same time, see https://github.com/mate-desktop/debian-packages/commit/f106be84565b5baae5d4e21c7a0dc9754574b9ea).
  4. Try running mate-session-save with --logout-dialog or --shutdown-dialog or other arguments.
    It will fail with an error message like this:
** (mate-session-save:2951): WARNING **: Failed to call logout: The name org.gnome.SessionManager was not provided by any .service files

It doesn't work as it's 1.11 version of the tool, so it tries to use org.gnome.SessionManager (after b01c417) - but the currently running session still uses org.mate.SessionManager.

This affects the apps or applets that rely on mate-session-save to provide logout/shutdown ability (e.g. mintMenu): you can't log out or shut down the system. Of course the issue will be gone on the next session run, but... 😄

This doesn't affect the built-in menu and menu-bar applets. They use panel's own code which still uses org.mate.SessionManager at the time. (Well, if you upgrade the panel to 1.11 as well, then restart it via killall mate-panel, then it will cease to work; but would you do that? 😄)

@raveit65
Copy link
Member

But a session restart after update of all affected packages should help?

@monsta monsta added this to the 1.12 milestone Oct 21, 2015
@monsta
Copy link
Contributor Author

monsta commented Oct 21, 2015

Yes, or some other solution.

@clefebvre @flexiondotorg @willysr @posophe @obache
So, we really need to solve this before 1.12 release - either upstream or in all distros...
Thoughts guys?

@willysr
Copy link
Member

willysr commented Oct 21, 2015

upstream is preferred

@monsta
Copy link
Contributor Author

monsta commented Oct 21, 2015

I was actually wondering how we'd solve it 😄

@raveit65
Copy link
Member

dowstream maintainers need to do the update in one rush and marked it as 'restart is needed', if they are brave enough to update in a running release cycle ;)

@monsta
Copy link
Contributor Author

monsta commented Oct 21, 2015

The problem is the failure of the usual tools for restarting (until the next session run)... if you use mintMenu, for example.

@monsta
Copy link
Contributor Author

monsta commented Oct 21, 2015

Ok guys, here's one possible solution in #104, please test if you can 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants