On 09/20/2014 01:11 PM, Fernando de Oliveira wrote:
> On 19-09-2014 17:40, Fernando de Oliveira wrote:
>> On 19-09-2014 17:02, Armin K. wrote:
>
>
>>> As I said, it needs to use ConsoleKit's PAM module manually or include
>>> system-session.
>>
>> Well this one is the machine working fine. It does not need to be fixed.
>> The other doesn't work fine, needs a fix. But let's continue the
>> discussion here.
>>
>> Forgive my ignorance, but I really don't understand: "it needs to use
>> ConsoleKit's PAM module manually or include system-session". I tried to
>> add the line
>>
>> account include system-account
>>
>
>
> Armin, thank you for helping me.
>
> I know I have done something wrong in this system, but configurations of
> what I search are identical.
>
> I don't exactly understand PAM and commented it, when included LXDM in
> the book. The lxdm PAM file there was what worked for me, then, but not
> now. So, please, I am willing to follow instructions, but sometimes my
> efforts are useless, because am not familiarized with PAM.
>
> One thing I studied was the output of lsof -c lxdm, so I obtain also
> lxdm-binary and lxdm-greeter. There are two, lxdm-greeter-{gdk,gtk},
> cannot tell wich one is referred to below, but certainly it the gtk one
> we see in the screen. Both, broken and working machines, seem to have
> the same output, to the best of my eyes, and both seem to be using PAM
> and ConsoleKit.
>
> Again, shutdown/reboot buttons don't work and no users list.
> I believe AccountsService is responsible for providing user list. At least it is for lightdm and gdm. > There has been many reports in the web of both problems. > > I am not worried by myself, don't even use lxdm in normal LFS machines. > But I am sure the user will want it working fine. So, any help is much > appreciated > > Below, the output columns are: > > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > > Broken > > $ sudo lsof -c lxdm | grep -E 'pam|connect' > [sudo] senha de fernando: > lxdm-bina 5664 root mem REG 8,2 173905 291316 > /lib/libpam.so.0.83.1 > lxdm-bina 5664 root mem REG 8,2 22996 302420 > /usr/lib/libck-connector.so.0.0.0 > lxdm-gree 5681 root mem REG 8,2 173905 291316 > /lib/libpam.so.0.83.1 > lxdm-gree 5681 root mem REG 8,2 22996 302420 > /usr/lib/libck-connector.so.0.0.0 > > Good: > > $ sudo lsof -c lxdm | grep -E 'pam|connect' > [sudo] senha de fernando: > lxdm-bina 2526 root mem REG 8,1 173741 425003 > /lib/libpam.so.0.83.1 > lxdm-bina 2526 root mem REG 8,1 22996 430463 > /usr/lib/libck-connector.so.0.0.0 > lxdm-gree 2967 root mem REG 8,1 173741 425003 > /lib/libpam.so.0.83.1 > lxdm-gree 2967 root mem REG 8,1 22996 430463 > /usr/lib/libck-connector.so.0.0.0 > > Hmm ... So LXDM links to the consolekit library? Few packages do that. Have you tried reinstalling ConsoleKit on the "broken machine"? If I recall correctly, GDM hardcoded a path to some consolekit binary that used to set up the daemon. Do you know if that's the case for LXDM? And if so, is the path correct? Otherwise, I'm out of ideas. -- Note: My last name is not Krejzi.
signature.asc
Description: OpenPGP digital signature
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
