On Tue, 24 Dec 2013 23:52:50 +0100 Vincent Lefevre <vinc...@vinc17.net> wrote:
> No, the menu is refreshed since when I install or remove systemd + > libpam-systemd, then log out, I can see changes. This is because when you log out, you create a new lightdm-gtk-greeter process and you see the change. However, inside one given lightdm-gtk-greteer process, the power_menu remains static. When libpam-systemd is removed, lightdm does not have anymore its own logind session. If no one else is logged, there is no more multi-session and the full power_menu can show up. If both libpam-systemd and systemd are removed I guess the lightdm_get_can_* () tests switch to consolekit and upower. > I haven't tried installing or removing systemd + libpam-systemd from > a VT while there's no user X session. I tried but as systemd is PID1, I just removed libpam-systemd and restarted systemd-login.service. I had to login with lightdm and logout to see the change (by running a new lightdm-gtk-greeter process). > > Shouldn't it run the lightdm_get_can_* () test at runtime when the > > user opens the power_menu ? > > When the user opens the menu would be the best, IMHO. I do not know how to achieve this. The best I could do to remove the gtk_widget_hide calls. The 4 items in the menu show up and the action fails when permission is not granted. But it is not user friendly since no feedback is given. Moreover, there is still this inconsistent behavior between shutdown and reboot (respectively suspend and hibernate) in case of multiple-sessions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org