On 19.9.2014 21:41, Fernando de Oliveira wrote:
On 19-09-2014 16:01, Armin K. wrote:
On 19.09.2014 20:42, Fernando de Oliveira wrote:
On 19-09-2014 12:37, Armin K. wrote:
On 19.09.2014 15:59, Fernando de Oliveira wrote:
2. lxdm: don't know why, in this system, it cannot poweroff/reboot and
does not show the user list. If I press poweroff, and click in the form
to enter the name, but only enter and enter, it does poweroff. Or after
trying to poweroff, if I login, imediately it starts powering off. There
is an easy work-around, but I would like to discover why in the older
dev machine it works. Spent most day yesterday trying to solve this.
Do you have ConsoleKit set up (with PAM)?
Yes, I do. Since the time when you solved a problem with gparted, I
always do it. What I don't understand is that lxdm starts, but does not
load polkit nor ConsoleKit.
You need to explicitly include system-session into lxdm PAM file or
include consolekit pam module like done in systems-ession.
Just to be sure we are talking about the same thing. LXSession is OK.
However, LXDM, just started by the bootscript is unable of
shutdown/reboot. Also, it is configured to show the users list. In my
previous dev machine both work fine. Th the best of my searches, Both
systems are equally configured.
LFS75-dev:
fernando [ ~ ]$ pgrep -l kit
2725 polkitd
2861 console-kit-dae
fernando [ ~ ]$ pgrep -l cups
2312 cupsd
LFS76-dev:
Last login: Fri Sep 19 14:55:34 2014 from 192.168.0.162
fernando [ ~ ]$ pgrep -l kit
4646 polkitd
fernando [ ~ ]$ pgrep -l kit
4646 polkitd
fernando [ ~ ]$ pgrep -l cups
4511 cupsd
Funny, I did something and it is starting polkitd but not console-kit-dae.
Very strange is that the pid's are very different from one machine to
the other.
What are the contents of /etc/pam.d/lxdm and /etc/pam.d/system-session
on both systems?
The same, I really beieve:
fernando [ ~ ]$ hostname
VMWLFS75eudev
fernando [ ~ ]$ cat /etc/pam.d/lxdm
#%PAM-1.0
auth required pam_unix.so
auth requisite pam_nologin.so
account required pam_unix.so
password required pam_unix.so
session required pam_unix.so
As I said, it needs to use ConsoleKit's PAM module manually or include
system-session. You are good to copy config file from KDM (KDE
Workspace) and try again. PAM Module should fire up ConsoleKit when
session is started unless LXDM has a separate process for greeter that
doesn't register any session.
fernando [ ~ ]$ cat /etc/pam.d/system-session
# Begin /etc/pam.d/system-session
session required pam_unix.so
# End /etc/pam.d/system-session
# Begin ConsoleKit addition
session optional pam_loginuid.so
session optional pam_ck_connector.so nox11
# End ConsoleKit addition
fernando [ ~ ]$ hostname
VMWLFS76
fernando [ ~ ]$ cat /etc/pam.d/lxdm
#%PAM-1.0
auth required pam_unix.so
auth requisite pam_nologin.so
account required pam_unix.so
password required pam_unix.so
session required pam_unix.so
fernando [ ~ ]$ cat /etc/pam.d/system-session
# Begin /etc/pam.d/system-session
session required pam_unix.so
# End /etc/pam.d/system-session
# Begin ConsoleKit addition
session optional pam_loginuid.so
session optional pam_ck_connector.so nox11
# End ConsoleKit addition
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
