Sent: Friday, September 01, 2017 at 11:25 PM From: "Ken Moffat" <[email protected]> To: "BLFS Support List" <[email protected]> Subject: Re: [blfs-support] Seg fault when starting Gnome On Fri, Sep 01, 2017 at 10:48:18PM +0200, Cliff McDiarmid wrote: > I have included Strace readouts, as attachments, both from the command line > and from Twm. They are similar, but there is nothing obvious. Calls seem to > be satisfied, unless a more experienced eye can see something. If someone has > the time I would appreciate it. > > Cliff
>But whatever it is, it looks as if *something*, perhaps related to >that EPERM, got logged in a journal. Maybe it only says that things >got killed. >I know almost nothing about current systemd, but is it possible this >got logged differently, i.e. maybe it needs some different magic >words when you use journalctl or whatever it is called (and by this >stage I suspect the words will be blue :) Thanks Ken. I'm now convinced that this problem, i.e. a brand new gnome session won't start, is because of no session id for the user(or for root for that matter) As the followers of Systemd will know pam_systemd registers user sessions with the systemd login manager, systemd-logind.service. Loginctl repeatly shows no session after logging in as a user(or root). I've trawled Google for advice on WHY no session would not be created and found very little. Do any of you know why this might not happen? I can't see the point in just reinstalling Pam and Systemd. I've checked various conf. files and made additions and then subtractions when it didn't work. Any advice appreciated. Cliff -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
