On Fri, Dec 2, 2016 at 8:30 PM, Ken Moffat <[email protected]> wrote:
> On Tue, Nov 29, 2016 at 01:32:18AM +0000, Ken Moffat wrote:
>> On Mon, Nov 28, 2016 at 01:59:26PM -0700, Roger Koehler wrote:
>> > On Mon, Nov 28, 2016 at 1:55 PM, Douglas R. Reno <[email protected]> 
>> > wrote:
>> > >
>> > >
>> > > On Mon, Nov 28, 2016 at 2:48 PM, Roger Koehler 
>> > > <[email protected]>
>> > > wrote:
>> > >>
>> > >> It crashes for me, too, with the latest xorg-server. If I go back to
>> > >> the previous version of xorg-server and libXfont, it works.
>> > >>
>> > >
>> > > I don't have xorg-server-1.19 on my workstation, I'm still at 1.18.x. I 
>> > > do
>> > > have the latest libXfont though.
>> >
>> > That may be the issue. Try libXfont 1.5.2.
>> I guess you meant "try libXfont-1.5.1 ?"  The new font lib is
>> libXfont2.
>>
>> I assume both need to be old - with 1.5.1 and 1.19.0 it is still
>> broken for me.
>>
>> Raised upstream at https://sourceforge.net/p/lxde/bugs/842/
>>
> I haven't made any progress on this.  According to upstream, lxdm
> doesn't reference libXfont, and it works on fedora25 with
> libXfont-1.5.2 and xorg-server-1.19.0.
>
> The segfault is after glibc seems to think my locale is
> ANSI_X3.4-1968 and failing to convert the UTF-8 message.  Root's
> locale when running lxdm via gdb was en_GB.UTF-8.
>
> Fedora are using lxdm-git : I tried that but it too segfaulted for
> me - I didn't bother to look at a bt for the moment, so I guess it
> might be different.
>
> I'm starting to wonder if something in current glibc broke this,
> but basically I'm flailing around and trying to clutch at straws.
>
> If I can't make any progress in the next few days, I guess I'd
> better raise a BLFS ticket asserting that this is broken.

Could be the kernel.  I just rebuilt my system with all the latest
(SVN) packages except for the kernel.  I built with linux 3.16.39, and
lxdm works fine. I am on an intel x86_64 laptop.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to