-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Comments
But a session restart after update of all affected packages should help? |
Yes, or some other solution. @clefebvre @flexiondotorg @willysr @posophe @obache |
upstream is preferred |
I was actually wondering how we'd solve it 😄 |
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 ;) |
The problem is the failure of the usual tools for restarting (until the next session run)... if you use mintMenu, for example. |
Ok guys, here's one possible solution in #104, please test if you can 😄 |
Steps to reproduce:
mate-desktop
to 1.11 (see https://github.com/mate-desktop/debian-packages/commit/aca038f1235bb2d5801ee56bd69fb277cca0d376).mate-session-manager
to 1.11 (also it's better to upgrademate-settings-daemon
to 1.11 at the same time, see https://github.com/mate-desktop/debian-packages/commit/f106be84565b5baae5d4e21c7a0dc9754574b9ea).mate-session-save
with--logout-dialog
or--shutdown-dialog
or other arguments.It will fail with an error message like this:
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 usesorg.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
andmenu-bar
applets. They use panel's own code which still usesorg.mate.SessionManager
at the time. (Well, if you upgrade the panel to 1.11 as well, then restart it viakillall mate-panel
, then it will cease to work; but would you do that? 😄)The text was updated successfully, but these errors were encountered: