Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#804165: lightdm: Options reboot,suspend,hibernate are all greyed out

251 views
Skip to first unread message

Frank McCormick

unread,
Nov 5, 2015, 11:30:03 AM11/5/15
to
Package: lightdm
Version: 1.16.3-1
Severity: normal


Updated Debian Sid a few days ago after not updating for a week.
Now all the options on the Lightdm screen such as reboot, hibernate, suspend are
greyed out. Have to reboot and halt from a terminal in the
window manager


-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.2.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lightdm depends on:
ii adduser 3.113+nmu3
ii dbus 1.10.2-1
ii debconf [debconf-2.0] 1.5.57
ii libaudit1 1:2.4.4-4
ii libc6 2.19-22
ii libgcrypt20 1.6.4-3
ii libglib2.0-0 2.46.1-2
ii libpam-systemd 227-2
ii libpam0g 1.1.8-3.1
ii libxcb1 1.11.1-1
ii libxdmcp6 1:1.1.2-1
ii lightdm-gtk-greeter [lightdm-greeter] 2.0.1-2

Versions of packages lightdm recommends:
ii xserver-xorg 1:7.7+12

Versions of packages lightdm suggests:
ii accountsservice 0.6.40-3
ii upower 0.99.3-1+b2

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
greeter-hide-users = False
[Seat:*]
greeter-hide-users=false
[XDMCPServer]
[VNCServer]


-- debconf information:
lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm

Agustin Martin

unread,
Feb 13, 2017, 7:10:02 AM2/13/17
to
On Thu, Nov 05, 2015 at 11:22:04AM -0500, Frank McCormick wrote:
> Package: lightdm
> Version: 1.16.3-1
> Severity: normal
>
>
> Updated Debian Sid a few days ago after not updating for a week.
> Now all the options on the Lightdm screen such as reboot, hibernate, suspend are
> greyed out. Have to reboot and halt from a terminal in the
> window manager

Hi,

I have also met this problem from time to time, appearing and disappearing
with some upgrades.

However, since systemd-shim 10.3 was uploaded to sid this problem
disappeared in my sid box (running lightdm 1.18.3-1). That upload fixes

https://bugs.debian.org/844785 [systemd-shim not fully compatible with systemd 232]

> Forgot to add this is happening under sysvinit not under systemd

Same here. Did that systemd-shim upload fix the problem for you?

Regards,

--
Agustin

Beardy

unread,
Jan 29, 2022, 8:10:04 AM1/29/22
to

Simply manually making pam_systemd.so a symlink to pam_elogind.so gets this working.

 

For what it’s worth.

 

I have no idea if making such a symlink as part of the install script if pam_systemd.so isn’t present  is permitted by Debian “POLICY”, however, it works....

Even if it would mask similar cases where things only look for the system variant.

Caretaker

unread,
Feb 27, 2022, 6:50:03 AM2/27/22
to

Given the tests coded in:

liblightdm-gobject/power.c

using org.freedesktop.login1 testing for each of Suspend, Hibernate, Restart and Shutdown

are failing & shouldn’t regardless if libpam_systemd or libpam-elogind is in use, it’s possible this bug is

a problem in policykit-1 which has been somewhat heavily hacked at to provide support for both

without having to compile different versions against different libraries.

 

It might be worth a conversation with the maintainers of said package to determine exactly who’s bug

this actually is.

 

I vaguely seem to recall that when I compiled policykit-1 v 0.115 (what experimental had at the time)

Against libelogind-dev rather than libsystemd-dev on a system using sysvinit-core and openrc and

also using the patch referenced here:

https://gitlab.freedesktop.org/polkit/polkit/issues/29

Then this issue went away.  My memory may be playing me tricks however.

 

Even though I didn’t do it properly & just used an equivs package & a symlink from libelogind.pc

to libsystemd.pc in order to fool the build-deps & actually build the packages.

 

I’m afraid that doing the job properly or determining exactly what’s going on here is slightly above

my skill level.  Frankly I wish I could tell & provide a patch for whichever package is at fault.

 

 

0 new messages