https://bugzilla.novell.com/show_bug.cgi?id=856773 https://bugzilla.novell.com/show_bug.cgi?id=856773#c1 Guido Berhörster changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|Usability |X11 Applications InfoProvider| |carlos.e.r@opensuse.org --- Comment #1 from Guido Berhörster 2013-12-27 10:58:09 UTC --- Is this actually any different from https://bugzilla.novell.com/show_bug.cgi?id=846914? Please provide the same information as in that bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=856773 https://bugzilla.novell.com/show_bug.cgi?id=856773#c3 Guido Berhörster changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gber@opensuse.org Component|X11 Applications |Basesystem AssignedTo|bnc-team-xfce@forge.provo.n |meissner@suse.com |ovell.com | --- Comment #3 from Guido Berhörster 2013-12-27 16:44:40 UTC --- (In reply to comment #2)

There are, of course, other users logged in on the same seat, MIND: the same seat.

But I want the root cause of this investigated, the decision to ask for root authorization at all, when it is not asked for powering down the machine or rebooting it. The policy is inconsistent.

Thus I have reported against usability, not XFCE.

The "root cause" are the policykit defaults defined in /etc/polkit-default-privs.standard: org.freedesktop.login1.power-off-multiple-sessions auth_admin_keep:auth_admin_keep:yes [...] org.freedesktop.login1.reboot-multiple-sessions auth_admin_keep:auth_admin_keep:yes [...] org.freedesktop.login1.hibernate-multiple-sessions auth_admin_keep So reassigning this to the polkit-default-privs bugowner.

There is also the problem that the password prompt goes behind another dialog despite being modal.

That is an entirely different issue and probably requires some reworking of the logout dialog of xfce4-session, please file a bug upstream against xfce4-session at https://bugzilla.xfce.org/enter_bug.cgi?product=Xfce4-session and attach the screenshot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=856773 https://bugzilla.novell.com/show_bug.cgi?id=856773#c5 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com AssignedTo|bnc-team-screening@forge.pr |meissner@suse.com |ovo.novell.com | --- Comment #5 from Marcus Meissner 2013-12-28 10:13:25 UTC --- please run loginctl list-sessions if there are multiple users at seat0 this privilege is meant to avoid users killing other users sessions. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=856773 https://bugzilla.novell.com/show_bug.cgi?id=856773#c7 --- Comment #7 from Carlos Robinson 2013-12-28 12:57:35 UTC --- (In reply to comment #6)

(In reply to comment #5)

...

please run

loginctl list-sessions

if there are multiple users at seat0 this privilege is meant to avoid users killing other users sessions.

Carlos already said that that is the case and was asking about the inconsistency between shutdown/reboot being allowed from the active session while suspend/hibernate requires admin authentication:

Correct, that's the point. I have a root session on tty1, which is also me, of course. IMO, there is no point in asking for root's password to hibernate and not to power off. Besides, the user can pull the cable and batteries. It is also very inconvenient not to be able to hibernate if the machine is a laptop, or it is an emergency like low battery power (laptops and desktops on UPS). The dangerous operation is halt, not hibernate. Hibernate preserves processes. This situation is similar to users not being able to setup printers, as Mr Linus pointed out some time ago. At worst, this should be easily configurable in YaST, so that we have an easy choice to impose strict policies or not. Suggest "strict, local user only, relaxed". Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=856773 https://bugzilla.novell.com/show_bug.cgi?id=856773#c9 --- Comment #9 from Carlos Robinson 2014-01-07 01:12:17 UTC --- I'd like to point out some more findings after upgrading my laptop from 11.4 to 13.1. I connected to my laptop from my desktop machine via "ssh -Y ...", run gkrellm, and a few more things. Yet I could suspend the laptop by closing the lid, or hibernate it by touching the power button, or via main menu. Neither option requested root password and succeeded - when several users were remotely connected. This should be against that policy! Then I opened a local text console session. Suspend still worked fine. Hibernation, though, failed. If triggered from the menu, I got the afore mentioned issue of having the prompt for password behind the logout dialog. If triggered from power button, or lid close (configure change on purpose for testing this situation), the screen showed the root password prompt, then it faded to black. Notice that in this situation the user will hardly see the password notice (no time to read it), and might store the laptop inside the bag, CAUSING FIRE DANGER! I'm not kidding, someone complained of a similar event on the forums about a month ago. His laptop overheated when it was supposed to hibernate and self-destroyed. Yes, he should check that the computer does power off, but he might be on a hurry, and he be used to hibernation always working, if this is the first time he has a second local session running. At a minimum, the user running on battery could close the lid assuming hibernation, which does not happen, the battery would run out and he could lose data. Gentlemen, this is not good. (To me this is no longer an issue, I'll run "sudo pm-hibernate" without password. To others...) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.