Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernel over the weekend?)

2002-09-30 Thread Maxim Sobolev

On Sun, Sep 29, 2002 at 12:17:54PM -0700, Eric Anholt wrote:
 On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote:
  Does this bug effect -stable? It only showed up in -current recently.
  Isn't it a bigger chance that something on the FreeBSD side made this bug
  much more visible?
  
  On Sun, 29 Sep 2002, Maxim Sobolev wrote:
  
   I think it should be fixed in FreeBSD ports before 4.7, because it
   is really annoying when server crashes without any particular
   reason.
  
   Eric, what do you think about it?
  
   -Maxim
 
 From what I had heard on the lists it was only a thing that happened
 when people upgraded kernels, and that it had stopped after some date of
 kernel.  I hadn't experienced it, so I ignored it.  I don't know about
 that link posted, I thought that was a mozilla bug that was supposed to
 be fixed.

I don't think that it is related to kernel (what kernel has to do with
Type1 font renderer in X server???). I'm seeing this problem when trying
to open MS Word document in AbiWord, perhaps a bug in AbiWord itself,
but IMO no application should be able to crash the server, so that we
need to fix it ASAP.

-Maxim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)

2002-09-29 Thread Frode Nordahl

Hey,

On Sun, 2002-09-29 at 14:51, walt wrote:
[snip]
 
 I wonder if it could find the very annoying crashes in the X server.
 
 -- 
 I'm sick of hearing about how big my Beziers are!

I found this on the Xpert mailinglist:
http://www.xfree86.org/pipermail/xpert/2002-June/018300.html

Seems like this won't get fixed until XFree86 4.3.0, but the bug seems
to be in the Type1 font handler only. (a call to abort())

I have removed it from my XFree86 config now, and I'm hoping for no more
Bezier crashes :)


Mvh,
Frode Nordahl


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernel over the weekend?)

2002-09-29 Thread Maxim Sobolev

I think it should be fixed in FreeBSD ports before 4.7, because it
is really annoying when server crashes without any particular
reason.

Eric, what do you think about it?

-Maxim

On Sun, Sep 29, 2002 at 03:17:41PM +0200, Frode Nordahl wrote:
 Hey,
 
 On Sun, 2002-09-29 at 14:51, walt wrote:
 [snip]
  
  I wonder if it could find the very annoying crashes in the X server.
  
  -- 
  I'm sick of hearing about how big my Beziers are!
 
 I found this on the Xpert mailinglist:
 http://www.xfree86.org/pipermail/xpert/2002-June/018300.html
 
 Seems like this won't get fixed until XFree86 4.3.0, but the bug seems
 to be in the Type1 font handler only. (a call to abort())
 
 I have removed it from my XFree86 config now, and I'm hoping for no more
 Bezier crashes :)
 
 
 Mvh,
 Frode Nordahl
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)

2002-09-29 Thread Wesley Morgan

Does this bug effect -stable? It only showed up in -current recently.
Isn't it a bigger chance that something on the FreeBSD side made this bug
much more visible?

On Sun, 29 Sep 2002, Maxim Sobolev wrote:

 I think it should be fixed in FreeBSD ports before 4.7, because it
 is really annoying when server crashes without any particular
 reason.

 Eric, what do you think about it?

 -Maxim

 On Sun, Sep 29, 2002 at 03:17:41PM +0200, Frode Nordahl wrote:
  Hey,
 
  On Sun, 2002-09-29 at 14:51, walt wrote:
  [snip]
  
   I wonder if it could find the very annoying crashes in the X server.
  
   --
   I'm sick of hearing about how big my Beziers are!
 
  I found this on the Xpert mailinglist:
  http://www.xfree86.org/pipermail/xpert/2002-June/018300.html
 
  Seems like this won't get fixed until XFree86 4.3.0, but the bug seems
  to be in the Type1 font handler only. (a call to abort())
 
  I have removed it from my XFree86 config now, and I'm hoping for no more
  Bezier crashes :)
 
 
  Mvh,
  Frode Nordahl
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-current in the body of the message

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message


-- 
   _ __ ___   ___ ___ ___
  Wesley N Morgan   _ __ ___ | _ ) __|   \
  [EMAIL PROTECTED] _ __ | _ \._ \ |) |
  FreeBSD: The Power To Serve  _ |___/___/___/
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting thekernel over the weekend?)

2002-09-29 Thread Eric Anholt

On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote:
 Does this bug effect -stable? It only showed up in -current recently.
 Isn't it a bigger chance that something on the FreeBSD side made this bug
 much more visible?
 
 On Sun, 29 Sep 2002, Maxim Sobolev wrote:
 
  I think it should be fixed in FreeBSD ports before 4.7, because it
  is really annoying when server crashes without any particular
  reason.
 
  Eric, what do you think about it?
 
  -Maxim

From what I had heard on the lists it was only a thing that happened
when people upgraded kernels, and that it had stopped after some date of
kernel.  I hadn't experienced it, so I ignored it.  I don't know about
that link posted, I thought that was a mozilla bug that was supposed to
be fixed.

-- 
Eric Anholt [EMAIL PROTECTED]
http://people.freebsd.org/~anholt/dri/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting thekernel over the weekend?)

2002-09-29 Thread Frode Nordahl

On Sun, 2002-09-29 at 21:17, Eric Anholt wrote:
 From what I had heard on the lists it was only a thing that happened
 when people upgraded kernels, and that it had stopped after some date of
 kernel.  I hadn't experienced it, so I ignored it.  I don't know about
 that link posted, I thought that was a mozilla bug that was supposed to
 be fixed.

It seems like the bug has been present in XFree86 all the time.  But
some thing has changed in CURRENT that tickles this bug.

I started to experience this after I removed all ports and recompiled
XFree86 with the new GCC 3.2.1.

X also dies with signal 11 some times, so theres more to it than the
Bezier bug.

But if it is a CURRENT kernel or compiler issue, I don't understand why
/ how this should affect -STABLE / -RELEASE.

I'll take a backup of my current X installation and do some tests and
comparisons against the Aug 24 port build of XFree86.

I'll have to find a sure way to reproduce the abort() and / or SIGSEGV
failure first though.

 -- 
 Eric Anholt [EMAIL PROTECTED]
 http://people.freebsd.org/~anholt/dri/
 

--
Mvh,
Frode Nordahl


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernelover the weekend?)

2002-09-29 Thread Wesley Morgan

Yes, i don't see any -stable systems bombing out. But it _always_ occurrs
when typing. No matter what app... Sometimes in the linux opera, sometimes
in the konq address bar. I dont think it ever happened when typing in an
Xterm though.

On 29 Sep 2002, Frode Nordahl wrote:

 On Sun, 2002-09-29 at 21:17, Eric Anholt wrote:
  From what I had heard on the lists it was only a thing that happened
  when people upgraded kernels, and that it had stopped after some date of
  kernel.  I hadn't experienced it, so I ignored it.  I don't know about
  that link posted, I thought that was a mozilla bug that was supposed to
  be fixed.

 It seems like the bug has been present in XFree86 all the time.  But
 some thing has changed in CURRENT that tickles this bug.

 I started to experience this after I removed all ports and recompiled
 XFree86 with the new GCC 3.2.1.

 X also dies with signal 11 some times, so theres more to it than the
 Bezier bug.

 But if it is a CURRENT kernel or compiler issue, I don't understand why
 / how this should affect -STABLE / -RELEASE.

 I'll take a backup of my current X installation and do some tests and
 comparisons against the Aug 24 port build of XFree86.

 I'll have to find a sure way to reproduce the abort() and / or SIGSEGV
 failure first though.

  --
  Eric Anholt [EMAIL PROTECTED]
  http://people.freebsd.org/~anholt/dri/
 

 --
 Mvh,
 Frode Nordahl


-- 
   _ __ ___   ___ ___ ___
  Wesley N Morgan   _ __ ___ | _ ) __|   \
  [EMAIL PROTECTED] _ __ | _ \._ \ |) |
  FreeBSD: The Power To Serve  _ |___/___/___/
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: XFree86 crash, Bezier thing

2002-09-29 Thread walt

Wesley Morgan wrote:
 Yes, i don't see any -stable systems bombing out. But it _always_ occurrs
 when typing. No matter what app...

I've seen in most often when starting X/gnome.  Almost always happens
when gnome-panel is just appearing on screen.  No typing going on yet,
naturally.

If gnome-panel is using a TypeI font that might account for it.

Oddly, though, usually if I just type startx a second time it all
starts OK.  Later it may crash with mozilla also, of course.

I took TypeI out of my fonts-path and so far no more crashes, but
it's been less than 24 hours, so still a bit early to crow.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message