[marcuscom] gnome 2.28 + linux apps = SIGSEGV ?

[Jeremy Messenger]

On Fri, 06 Nov 2009 14:31:39 -0600, Boris Samorodov <bsam at ipt.ru> wrote:

> On Fri, 06 Nov 2009 06:32:58 -0600 Jeremy Messenger wrote:
>> On Fri, 06 Nov 2009 04:11:05 -0600, Boris Samorodov <bsam at ipt.ru> wrote:
>
>> > I faced a problem with 9-CURRENT and 8-STABLE:
>> >  
>> http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013061.html
>> >
>> > Both systems use gnome-2.28 from marcuscom. Can anybody use
>> > acroread8 with gnome-2.28? (I'm not sure but seems that skype
>> > and linux-realplayer get SIGSEGV as well.) Other 8-STABLE
>> > system with gnome from current ports tree works fine.
>
>> Interesting.... I can't run linux-opera in MC either. At first, I
>> thought  it might be related w/ security.bsd.map_at_zero and I didn't
>> bother to try  it (by either update RELENG_8 w/ fixes or try this
>> sysctl).
>
>> Until your email.... Makes me think that it might be related w/
>> print/freetype2, because of fontconfig is showing up in your ktrace?
>> Try  to downgrade the freetype2 and see if it helps? It's only thing
>
> Jeremy, good shot! It was fontconfig. I downgraded it to 2.6.0 and
> acroread now works.

Great, all we need to figure a solution now on a right target. ;-)

>> that I can  think of what change in MC related w/ font stuff, I will
>> need to check in  MC more. In the past, there was problem with linux
>> apps when Linux and  FreeBSD have different version of fontconfig
>> (cache stuff) at the same.  But this isn't in case as fontconfig isn't
>> update or change in MC.
>
> Is it? The version from MC was 2.7.3.

Oops, I was looked at the wrong terminal window (only knew about freetype2  
change but not fontconfig). :-) Yeah, MC does has fontconfig change. Must  
be cache issue just like before. Let me try to dig in the archives and see  
if I can find old thread about fontconfig as my memory is pretty fuzzy  
with this. Not sure if it's possible to use Linux's fc-cache to have  
seperate cache or have to force Linux's fontconfig to be upgraded.

I just remember that I am a person that reported this bug when someone  
updated fontconfig.

> Well, in any case, the kernel should not do SIGSEGV, isn't it?

No idea, I am no expert and no knowledge about what kernel should and  
shouldn't.

Cheers,
Mezz


-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org