Sent: Wednesday, August 30, 2017 at 7:10 PM
From: "Armin K." <[email protected]>
To: [email protected]
Subject: Re: [blfs-support] Seg fault when starting Gnome
From: "Armin K." <[email protected]>
To: [email protected]
Subject: Re: [blfs-support] Seg fault when starting Gnome
On 30.8.2017 19:06, Cliff McDiarmid wrote:
>
> Michael Shell wrote:
>
>> I found this:
>
>> https://www.linuxquestions.org/questions/linux-from-scratch-13/anyone-good-with-gnome3-4175608979/
>
>
> Yes seen that. That's what made me think that Pam, maybe, is a prerequisite for Gnome.
>
>
>> In any case, do let us know if PAM was to blame.
>
> Hi
>
> Well I did the following:
>
> Installed linux-pam as per BLFS instructions
>
> reinstalled Systemd as BLFS
>
>But did you configure PAM to use pam_systemd module? Your logs say
>
> Michael Shell wrote:
>
>> I found this:
>
>> https://www.linuxquestions.org/questions/linux-from-scratch-13/anyone-good-with-gnome3-4175608979/
>
>
> Yes seen that. That's what made me think that Pam, maybe, is a prerequisite for Gnome.
>
>
>> In any case, do let us know if PAM was to blame.
>
> Hi
>
> Well I did the following:
>
> Installed linux-pam as per BLFS instructions
>
> reinstalled Systemd as BLFS
>
>But did you configure PAM to use pam_systemd module? Your logs say
Well I followed the BLFS book to the letter
>otherwise.
> reinstalled Xorg server
>
> installed other packages that depend on PAM
>
> and no, PAM it would seem isn't to blame. Still getting messages about logind and PAM(see attached log). And from further digging it seems this message comes up for a variety of reasons not linked directly to PAM. So where from here. Thinking of running strace on the session and see the output.
>
> thanks
>
> Cliff
>
>
>
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
