[opensuse] SDDM Leap Question about configuration.
When I run a multiple user setup and several users are open. If I use sddm (but also lightdm) I cannot shutdown. I can just logout, one by one, from all users and then shutdown. Is there a way to shutdown the machine with one click, and in the same time gently(!) close down all open userinstances? Where would I have to set this? How would I have to set this? Thank you -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On February 13, 2017 2:45:20 AM PST, stakanov <stakanov@eclipso.eu> wrote:
When I run a multiple user setup and several users are open. If I use sddm (but also lightdm) I cannot shutdown. I can just logout, one by one, from all users and then shutdown. Is there a way to shutdown the machine with one click, and in the same time gently(!) close down all open userinstances?
Where would I have to set this?
How would I have to set this?
Thank you
Have you tried looking at the configuration files in sddm and lightdm for the methods each uses for this? This is usually tailorable within each DM, if for no other reason than they are used by various Linux distributions. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data lunedì 13 febbraio 2017 08:31:13, John Andersen ha scritto:
On February 13, 2017 2:45:20 AM PST, stakanov <stakanov@eclipso.eu> wrote:
When I run a multiple user setup and several users are open. If I use sddm (but also lightdm) I cannot shutdown. I can just logout, one by one, from all users and then shutdown. Is there a way to shutdown the machine with one click, and in the same time gently(!) close down all open userinstances?
Where would I have to set this?
How would I have to set this?
Thank you
Have you tried looking at the configuration files in sddm and lightdm for the methods each uses for this?
This is usually tailorable within each DM, if for no other reason than they are used by various Linux distributions. Yes and this is the weired question. With kdm that was easy, as you had the setting in yast. If you go to sddm you find:
[Autologin] Relogin=false User= [General] HaltCommand= RebootCommand= [Theme] Current=breeze-openSUSE CursorTheme=Breeze_Snow [Users] MaximumUid=65000 MinimumUid=1000 [XDisplay] DisplayCommand=/etc/X11/xdm/Xsetup MinimumVT=7 ServerPath=/usr/bin/X SessionCommand=/etc/X11/xdm/Xsession Now the weired thing is that the halt and the reboot command are empty. Because once you are in sddm you can click on reboot or on shutdown and it works. So it appears that something else governs this. My suspect would be that in opensuse this is done by PAM or by maybe systemd directly? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/13/2017 10:02 AM, stakanov wrote:
[General] HaltCommand= RebootCommand=
If you put in the systemctl shutdown command into the above will it work? (I don't know if is section applies when someone is logged in, or when some one is sitting at the sddm login screen. It may ask for a (root) password, which I believe is the correct thing to do when you boot a machine right out from under other users.) -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/13/2017 10:02 AM, stakanov wrote:
[General] HaltCommand= RebootCommand=
If you put in the systemctl shutdown command into the above will it work?
(I don't know if is section applies when someone is logged in, or when some one is sitting at the sddm login screen. It may ask for a (root) password, which I believe is the correct thing to do when you boot a machine right out from under other users.) Noop, I tried this already. That has no effect at all. That is why I think
In data lunedì 13 febbraio 2017 13:12:33, John Andersen ha scritto: that this section in the case of Leap is not used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-13 22:12, John Andersen wrote:
On 02/13/2017 10:02 AM, stakanov wrote:
[General] HaltCommand= RebootCommand=
If you put in the systemctl shutdown command into the above will it work?
Will not work unless you are root. If you are a user, it will wait or refuse till other users log out. Even an ssh session blocks it. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 02/13/2017 2:05 PM, Carlos E. R. wrote:
On 2017-02-13 22:12, John Andersen wrote:
On 02/13/2017 10:02 AM, stakanov wrote:
[General] HaltCommand= RebootCommand=
If you put in the systemctl shutdown command into the above will it work?
Will not work unless you are root. If you are a user, it will wait or refuse till other users log out. Even an ssh session blocks it.
Well, as I mentioned in the part you trimmed, I believe this is the correct behavior. Perhaps there should be some setting roor could make to allow shutdowns with other users logged in, but I am not aware of any. -- _____________________________________ ---This space for rent---
* John Andersen <jsamyth@gmail.com> [02-13-17 17:57]:
On 02/13/2017 2:05 PM, Carlos E. R. wrote: [....]
Will not work unless you are root. If you are a user, it will wait or refuse till other users log out. Even an ssh session blocks it.
Well, as I mentioned in the part you trimmed, I believe this is the correct behavior.
Perhaps there should be some setting roor could make to allow shutdowns with other users logged in, but I am not aware of any.
istr yast asked during original install if a <user> could do system shutdown. And I found it, yast2 -> sysconfig editor -> desktop -> display manager -> DISPLAYMANAGER_SHUTDOWN Description: Determine who will be able to shutdown or reboot the system in kdm. Valid values are: "root" (only root can shutdown), "all" (everybody can shutdown), "none" (nobody can shutdown from displaymanager), "auto" (follow System/Security/Permissions/PERMISSION_SECURITY to decide: "easy local" is equal to "all", everything else is equal to "root"). gdm respects the PolicyKit settings for ConsoleKit. Shutdown configuration can be done via the polkit-default-privs mechanism. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data lunedì 13 febbraio 2017 18:13:53, Patrick Shanahan ha scritto:
* John Andersen <jsamyth@gmail.com> [02-13-17 17:57]:
On 02/13/2017 2:05 PM, Carlos E. R. wrote: [....]
Will not work unless you are root. If you are a user, it will wait or refuse till other users log out. Even an ssh session blocks it.
Well, as I mentioned in the part you trimmed, I believe this is the correct behavior.
Perhaps there should be some setting roor could make to allow shutdowns with other users logged in, but I am not aware of any.
istr yast asked during original install if a <user> could do system shutdown.
And I found it, yast2 -> sysconfig editor -> desktop -> display manager -> DISPLAYMANAGER_SHUTDOWN
Description:
Determine who will be able to shutdown or reboot the system in kdm. Valid values are: "root" (only root can shutdown), "all" (everybody can shutdown), "none" (nobody can shutdown from displaymanager), "auto" (follow System/Security/Permissions/PERMISSION_SECURITY to decide: "easy local" is equal to "all", everything else is equal to "root"). gdm respects the PolicyKit settings for ConsoleKit. Shutdown configuration can be done via the polkit-default-privs mechanism. Correct.I have this to everybody as it is laptop. No reaction. This setting with KDM worked. With sddm it is stricktly ignored.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/13/2017 03:16 PM, stakanov wrote:
Correct.I have this to everybody as it is laptop. No reaction. This setting with KDM worked. With sddm it is stricktly ignored.
Are you required to keep SDDM? Could you not switch to KDM, or LightDM? Remember that SDDM is brand spankin new, and buggy and bloated, and another one of those things opensuse has foisted on us without so much as a warning. SDDM has problems with "seats" such that processes started by systemd on behalf of a user can not even be accessed by that user when he signs on. So no way to control your VirtualBox VMs that you launch at boot time via systemd except as sudo or root. This problem goes away with lightdm or KDM. I'm lead to believe KDM is deprecated, but it still might be available. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-13 23:55, John Andersen wrote:
On 02/13/2017 2:05 PM, Carlos E. R. wrote:
On 2017-02-13 22:12, John Andersen wrote:
On 02/13/2017 10:02 AM, stakanov wrote:
[General] HaltCommand= RebootCommand=
If you put in the systemctl shutdown command into the above will it work?
Will not work unless you are root. If you are a user, it will wait or refuse till other users log out. Even an ssh session blocks it.
Well, as I mentioned in the part you trimmed, I believe this is the correct behavior.
In the command line you get a chance to enter the root password and do poweroff.
Perhaps there should be some setting roor could make to allow shutdowns with other users logged in, but I am not aware of any.
You can run the command via sudo. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
In data martedì 14 febbraio 2017 00:20:17, Carlos E. R. ha scritto:
On 2017-02-13 23:55, John Andersen wrote:
On 02/13/2017 2:05 PM, Carlos E. R. wrote:
On 2017-02-13 22:12, John Andersen wrote:
On 02/13/2017 10:02 AM, stakanov wrote:
[General] HaltCommand= RebootCommand=
If you put in the systemctl shutdown command into the above will it work?
Will not work unless you are root. If you are a user, it will wait or refuse till other users log out. Even an ssh session blocks it.
Well, as I mentioned in the part you trimmed, I believe this is the correct behavior.
In the command line you get a chance to enter the root password and do poweroff.
Perhaps there should be some setting roor could make to allow shutdowns with other users logged in, but I am not aware of any.
You can run the command via sudo. This is the question. Is it the same? When I do the logoff via sddm this is sigterm right? And if I do it with terminal via sudo shutdown -h now, isn't this qualitatively different because applications get a sig kill (instead of sig term)? Maybe I am wrong. My worry is just that if I shutdown cronically for convenience with the above command I may destroy akonadi and its databases if e.g. kontakt is open on another account. In fact when I did shut down in the past with the kdm way, I never had e.g. Chromium complain that it was not shutdown correctly. Now Chromium and FF complain if I shutdown via console.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-14 00:29, stakanov wrote:
In data martedì 14 febbraio 2017 00:20:17, Carlos E. R. ha scritto:
Perhaps there should be some setting roor could make to allow shutdowns with other users logged in, but I am not aware of any.
You can run the command via sudo. This is the question. Is it the same?
Regarding the systemd command, when run as user it will not proceed if there is someone logged in still. It asks for the root password if you want to continue, so at that point it is the same as if you run the command via sudo or as root. I understand it asks politely all applications to finish, and after some time, forcefully kills them. It does not go via the desktop "logout" procedure, it does not give the chance for applications to ask the users how to save work. If the applications save things automatically on their own in the few seconds they are given to quit, that's fine. I doubt graphical sessions finish in the proper order - unless systemd is informed of what is the proper order - ie, they were started as a user process under the control of systemd.
Maybe I am wrong. My worry is just that if I shutdown cronically for convenience with the above command I may destroy akonadi and its databases if e.g. kontakt is open on another account.
In that case, it is best to logoff manually in all the accounts and sessions. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
In data martedì 14 febbraio 2017 00:48:48, Carlos E. R. ha scritto:
On 2017-02-14 00:29, stakanov wrote:
In data martedì 14 febbraio 2017 00:20:17, Carlos E. R. ha scritto:
Perhaps there should be some setting roor could make to allow shutdowns with other users logged in, but I am not aware of any.
You can run the command via sudo.
This is the question. Is it the same?
Regarding the systemd command, when run as user it will not proceed if there is someone logged in still. It asks for the root password if you want to continue, so at that point it is the same as if you run the command via sudo or as root.
I understand it asks politely all applications to finish, and after some time, forcefully kills them. It does not go via the desktop "logout" procedure, it does not give the chance for applications to ask the users how to save work. If the applications save things automatically on their own in the few seconds they are given to quit, that's fine. I doubt graphical sessions finish in the proper order - unless systemd is informed of what is the proper order - ie, they were started as a user process under the control of systemd.
Maybe I am wrong. My worry is just that if I shutdown cronically for convenience with the above command I may destroy akonadi and its databases if e.g. kontakt is open on another account.
In that case, it is best to logoff manually in all the accounts and sessions. Life was easier before knowing the answer to life, the universe and everything. But I am going to survive anyway. And then a multiuser session is rare these days I guess. But for my situation makes sense.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R. -
John Andersen -
Patrick Shanahan -
stakanov