Closing this bug as the original problem is solved in trusty.
The default logind (the system that performs the shutdown/restart)
allows an active session to perform this action. The greeter is an
active session so the user can shutdown and reboot from it even when
multiple sessions are open.
Marking it as Won't Fix in OEM priority project as the behaviour in
Trusty is completely different
** Changed in: oem-priority/precise
Status: In Progress = Won't Fix
** Changed in: oem-priority
Status: In Progress = Won't Fix
--
You received this bug notification because you are
This bug doesn't affect lightdm-gtk-greeter anymore. Currently (1.8
series) users can shutdown a machine from the greeter, but the shutdown-
dialog shows a warning that there are still users logged in and that
there is the chance for data-loss.
** Changed in: lightdm-gtk-greeter
Status:
** Tags added: ubuntu-desktop-trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when multiple accounts open
Status in The
** Changed in: gnome-session (Ubuntu)
Importance: Undecided = Medium
** Changed in: gnome-session (Ubuntu)
Status: Confirmed = Triaged
** Changed in: indicator-session (Ubuntu)
Status: In Progress = Triaged
** No longer affects: indicator-session (Ubuntu Precise)
** No longer
As with 13.10 the machine will shutdown without complaining regardless
which user demands it - thats also not the behaviour expected because my
unsaved work will be lost. this should be allowed only to administrator
or at least there should be a warning message.
--
You received this bug
** Also affects: gnome-session (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: policykit (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: indicator-session (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects:
** No longer affects: unity-greeter
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when multiple accounts open
Status in The
** Changed in: indicator-session
Importance: High = Medium
** Changed in: indicator-session (Ubuntu)
Importance: High = Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
Friday, 13:50 at school. The lesson finished, the ltsp server refused to
shudown and I wanted to catch the 14:00 bus to go home.
I pressed the power-off button at the back side of the system unit!
--
You received this bug notification because you are a member of Desktop
Packages, which is
I can't believe that this bug isn't a priority. It drives my parents nuts!
On Oct 5, 2013 7:51 AM, Aspasia Dilalou 861...@bugs.launchpad.net wrote:
Friday, 13:50 at school. The lesson finished, the ltsp server refused to
shudown and I wanted to catch the 14:00 bus to go home.
I pressed the
Any progress on this one?
It's very annoying on LTSP, where teachers can't shut down the LTSP
servers because e.g. 2 hours ago some student had a xorg crash, and even
if his thin client is now powered off, the user is still considered
logged on at the server because the ssh socket isn't yet
** Changed in: oem-priority
Assignee: James M. Leddy (jm-leddy) = Ara Pulido (apulido)
** Changed in: oem-priority/precise
Assignee: James M. Leddy (jm-leddy) = Ara Pulido (apulido)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Tags added: multiseat
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when multiple accounts open
Status in The Session
Alt A of Matthew seems to be fine!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when multiple accounts open
Status in The
** Changed in: gnome-session (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown
** Branch linked: lp:~mathieu-tl/indicator-session/logind-multiple-
session-lp861171
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does
This bug affects me on a fresh install of raring.
The difference with what has been described so far is that if (at least) one
user is logged in, and I try to shutdown from the loggin screen, it hangs
forever. Can we expect to have a fix released for raring soon?
--
You received this bug
Mathieu is fixing this in saucy at the moment. We should have a fix for
saucy as well as the SRU shortly. Thanks Mathieu!
** Changed in: unity-greeter (Ubuntu)
Assignee: Omer Akram (om26er) = (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages,
** Changed in: unity-greeter (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when
** Description changed:
- Selecting shutdown from the greeter does nothing when multiple accounts
- are open.
+ [Impact]
+
+ * A user tries to shut down their machine. They get confused because nothing
happens
+when they click shutdown.
+ * If someone else is logged in, they will have
** Changed in: indicator-session (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing
** Changed in: unity-greeter (Ubuntu)
Assignee: (unassigned) = Omer Akram (om26er)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does
** Changed in: oem-priority
Assignee: (unassigned) = James M. Leddy (jm-leddy)
** Changed in: oem-priority/precise
Importance: Undecided = High
** Changed in: oem-priority/precise
Assignee: (unassigned) = James M. Leddy (jm-leddy)
--
You received this bug notification because you
I've already done the 'affects me'.
But I'd like to point out that it affects me on Xubuntu Quantal (only
Precise is listed anywhere on the page at the moment).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
We could add a checkbox to the dialog that needs to be checked to be
able to select the destructive action, hmm, but it might be confusing
for the other choices. Or maybe an extra verification dialog box with
cancel as default (and maybe the checkbox here instead) that pops up
when selecting the
I'd say go for your Alt A, Robert, and I agree that an authentication
dialogue is better than the vanilla conf dialogue exactly like you say;
This will definitely make the general wife or brother pause to think
3 seconds before shutting down killing other sessions.
I guess that power button is
Robert, thank you. That looks a much better design, because it provides
a well-framed choice. I'd tack an Anyway onto the Shut Down button,
as a hint to those who didn't read the text that something risky is
about to happen.
People here have made statements of form It's no use asking for
I have no objection to an authentication dialog, as long as by default
it permits a non-admin user to shut down a machine without disk
corruption if he's physically present.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session
@Kai,
You're right. We have found that both behaviors, the one you describe
and the main related to this bug, have the same root: policykit
I haven't tried the patch commented by James (comment #33), but it's
maybe the solution you're searching for.
Anyway, if you want to do it by hand, the
Thank you so much to all the people that moved this bug the last week
!!!
But I think that most of you are moving in a different direction, and
all of the examples in the comments could been solved by the expected
behavior commented in post #20
(https://bugs.launchpad.net/ubuntu/+source/unity-
I think a goal should be to avoid forcing users to do unclean shutdowns with
the power button etc.
If I'm logged in but not at home and my wife wants to turn off the computer,
she should be able to even though she's not an admin.
--
You received this bug notification because you are a member
Here is an alternative dialog we can present. In this case you are able
to continue the shutdown process if you desire and continue with the
current PolicyKit behaviour. This option wouldn't be shown inside the
greeter though we could fix the PolicyKit issues there and resolve that
in the future.
Yes, but the destructive action shouldn't be the default button.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when multiple
It's a toss-up: the current behavior is mysterious, but the proposed
behavior would be vexatious. Ubuntu would be telling you that the other
accounts need to log out, but refusing to offer to do that.
I don't feel strongly about whether it should require admin-only
authentication or any-user
I agree that there isn't much point in limiting who should be able to
shut down the machine when accounts are logged in, when the user has
access to the power button anyway. I feel that any user should always
have the opportunity to cleanly shut down the machine via the GUI, not
allowing that is a
I would argue the current behavior is both mysterious and vexatious.
Ubuntu tells you nothing and refuses to do what you told it to do.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
For the record, it's not actually true that any user with a graphical
login will be in a position to reach the power button. Rebooting the
system out from other logged in users should require admin privileges.
--
You received this bug notification because you are a member of Desktop
Packages,
With a graphical login, not neccessarily.
With a graphical login on a local console (allow_active in policykit,
at_console in dbus, etc.), the user should not require admin privileges.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
What about this use case
- I am logged in as an administrator
- Suddenly, my brother next to me asks to log in to check his mails for 3
minutes.
- I move to the other room while he is logged (switched to another session)
in to a Standard session (mine is still on).
When I am back, I find the
@Hanine: What's preventing your brother from holding the power button
down for 3 seconds?
Forcing admin rights to perform actions that can by bypassed with
physical access would be inconsistent will all the other rights that are
currently granted to console users.
--
You received this bug
Here's another scenario: A laptop is shared by multiple members of a
household. User A is the admin, User B is not.
User B steps up to laptop with the intention of shutting it down to
leave with it. User A is currently logged in.
We have two choices here:
1- Present a warning dialog to User B
The could be locked in a cabinet so that it can't be hit by any user.
And since Ubuntu can't know, the behaviour must be configurable, and
only the default must be discussed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
If you have access to the console keyboard, by default you can use the
magic sysrq key to reboot the system.
The default should represent the most common scenario, which is physical
access. If someone has locked the computer up, the magic sysrq settings,
and the policykit default configuration
On Fri, Nov 30, 2012 at 07:01:03PM -, Marc Deslauriers wrote:
@Hanine: What's preventing your brother from holding the power button
down for 3 seconds?
The fact that your desktop is in a locked cabinet, obviously :-)
--
You received this bug notification because you are a member of
Just got done corresponding with seb128 about this, Robert Ancell said
patching the indicator to warn about other logged users should fix the
most common cases and not be too hard.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Branch linked: lp:~robert-ancell/indicator-session/lp-861171
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when multiple
The solution I have implemented in lp:~robert-ancell/indicator-
session/lp-861171 resolves this issue by changing the session indicator
to disallow shutdown or restart if more than one session is open.
This resolves the greeter issue:
old: Shutdown/restart silently failed.
new: Information dialog
After writing the previous comment I realised we can just have the
behaviour change in the greeter and not in the session if we want.
I think it is better with this solution though because:
- The dialog is more consistent between session and greeter
- The current PolicyKit dialog is bad because
** Attachment added: Screenshot of shutdown dialog (inside session) when
multiple users logged in
https://bugs.launchpad.net/unity-greeter/+bug/861171/+attachment/3447472/+files/shutdown-dialog-greeter-multi-session.png
--
You received this bug notification because you are a member of
** Attachment added: Screenshot of shutdown dialog (inside session) when
multiple users logged in
https://bugs.launchpad.net/unity-greeter/+bug/861171/+attachment/3447471/+files/shutdown-dialog-multi-session.png
--
You received this bug notification because you are a member of Desktop
I have a slight issue with this design...it's encouraging people who are
on the console to force a power off if they don't care/don't have the
credentials of the other active sessions. Shouldn't we give the
possibility of still obtaining a policykit dialog to force shutdown?
Possibly something
Actually, the policykit dialog should give sufficient rights to
whoever's at the console, not just system administrators. There is no
reason to ask for authentication to shut down a machine when someone's
on the console and presumably has access to the power button.
--
You received this bug
This also happens when you choose to shutdown inside a session and
another user is logged in. Then instead of shutting down you are only
logged out.
This really sucks. Because I trust my computer to shutdown when I click
shutdown. So sometimes I leave the room after shutting down and returns
Anyone that is interested in a workaround can pick up a new policykit
policy here:
https://launchpad.net/~canonical-hwe-team/+archive/sputnik-policykit
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
@Marius,
Maybe kdm handles it better. That's why we're asking for improve this
feature in lightdm.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from
@ethanay,
Terminal or tty shouldn't be the only way to solve this problem. There's
a lot of people that hasn't this knowledge. And request that the system
does what it seems to be doing (but it doesn't) is, imho, the simple way
to solve it.
Regards,
--
You received this bug notification
@Matthew,
Your approach related to the prompt / secondary text seems to be fine.
In addition, more information related to other users logged before halt or
reboot could be useful. You can see some examples at comments #20 and #22. By
the way, I'm not so sure if this behavior is about
@Matthew,
Maybe you should add what we were talking about in this bug:
Allow to a 'no admin user' to shutdown/reboot the system if he/she is
the only user logged in.
Kind Regards,
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
why can't the greeter just say, X user(s) is/are still logged in.
Please log out of all accounts before attempting to shut down or
reboot. and ignore all the nastly permissions stuff??
If an admin really needs to shut down, it's easy enough to do via
terminal or tty. are there really daily use
** Changed in: oem-priority
Status: New = In Progress
** Changed in: oem-priority/precise
Status: New = In Progress
** Tags added: rls-r-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
And in the case that yourself is logged in at the console, no admin
password should be asked. I think kdm handles this better.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/precise
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
I used this particular problem as an example when redesigning the
PolicyKit prompt. https://wiki.ubuntu.com/AccountPrivileges#The_prompt
(In that sketch I also show fingerprint authentication, but you can
ignore that part.)
--
You received this bug notification because you are a member of
@Florian,
Nice idea!!
Some examples for the notification if there are some users are logged:
You and Florian are logged.
You, Florian, ethanay, daniel, Lionel and 3 more are logged.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Why are you talking about notifications and password prompts, the computer
should shut down (by default) of course!
It could prompt and say X is logged in, are you really sure you want to shut
down? but nothing more. If an admin wants to disable it there should be a way
to do that instead.
@Ernst Sjöstrand (ernstp)
That's pretty much what everyone else is already saying: By default when
you shutdown with other users logged in, it should prompt saying other
users are logged in, are you sure?, and then let you shutdown if you hit
ok. The other suggestions here are just ways to make
Ernst,
If you follow the comments you'll figure out that some time the computer
should shut down and some time it shouldn't, depending on the user
requesting the shut down and the amount of users logged in.
After some comments, we're proposing some ideas of how it could be shown
or communicated
Am Mon, 01 Oct 2012 21:36:26 -
schrieb parq 861...@bugs.launchpad.net:
@ethanay
I agree with you.
This is just an example of the expected behavior, imho:
a. Normal user + other users logged:
You just can't turn off the computer because there are more users
logged. Please talk to
so, to recap:
1. user should get communication from OS regardless of whether they are admin
a. normal users should get a message explaining why restart / shut down has
failed (because other users are still logged in; otherwise it just looks like
unexpected behavior)
b. admin users should get a
@ethanay
I agree with you.
This is just an example of the expected behavior, imho:
a. Normal user + other users logged:
You just can't turn off the computer because there are more users logged.
Please talk to an admin. [ok]
b. Admin user + other users logged:
There are more users logged in
@Florian,
You're right!! This isn't a full solution.
It's only a workaround for those (like me) that want a partial solution
and accept the (high) risk.
As I have said in a previous comment
(https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/861171/comments/13) the full solution is
@parq: I'd prefer to get an error message that tell me why I can't shut
down with an option to shut down anyway. Just shutting down may lead to
data loss so that's usually not what I want.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@Matthew,
At least bug #86 seems to have the same core problem.
I've published a workaround in bug #86 that i'm going to copy here,
and fix this bug (#861171) and bug #86.
I think the problem is only related to PolicyKit, because this doesn't
handle correctly the 'auth_admin_keep'
Workaround:
As I've commented previously, this partial solution is to modify this
file:
/usr/share/polkit-1/actions/org.freedesktop.consolekit.policy
and change:
auth_admin_keep
to:
yes
Edit the file /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy
using your favorite text
I see this bug has triaged a lot of packages/apps.
I think this is a PolicyKit only behavior, and could be some related
issue with greeter (lightdm o gnome) related on how to handle the
request of admin password from PolicyKit.
The rest of packages/apps should be, imho, freed from this bug.
--
También he publicado cómo resolver este problema en español:
http://elblogdeparq.blogspot.com.es/2012/08/ubuntu-no-se-puede-
reiniciarapagar-si.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
This bug report is about Selecting shutdown from the greeter. Bug
621714, bug 660120, bug 747330, bug 86, and bug 872054 have all been
marked as duplicates but they all specifically mention trying to shut
down or restart from inside a session. Either this bug report is overly
precise, or those
Can you tell who marked those bugs as duplicates? If it wasn't Robert
Ancell, they could probably be unmarked. There's a possibility the same
codepath is involved in being at the greeter vs. in a session, but he's
likely the only person active here who would know for sure.
--
You received this
That wasn't Robert (you can check by appending /+activity to each bug
url).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when
Affects me also as a 64 bit install of 12.04 with four user accounts. A
warning and a password over-ride should be generated, as per behaviour
in 10.04. As it stands non-admin user cannot now shut down normally at
all if another user is logged in, even if the other user's processes are
in 'zombie'
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Also affects: policykit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-session (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: policykit (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
84 matches
Mail list logo
